Keeping local modifications

[Randall Wood]

I work in an unindexed ports tree to maintain my ports.

If a portfile is in the current working directory, the port command  
can act on that port as if it were any other port by using the port  
command without naming the port to be installed/uninstalled etc.

The only command that does not work in this fashion is "upgrade,"  
however, the command
"port upgrade x" is functionally equivalent to "port deactivate x ;  
port install x"

On 23 Oct 2006, at 21:04, Vincent Lefevre wrote:

> On 2006-10-23 14:48:11 -0700, Blair Zajac wrote:
>> It's very rare that I have any local changes in my ports that I  
>> wouldn't
>> want to see or would be inappropriate for all MacPorts users.
>
> But sometimes, a new version may be more buggy than an old one
> (possibly with local modifications). So, it may be useful to have
> a location that has the precedence over the (version, revision).
>
> However, what would be fine, is to have both. For instance, each URL
> of the sources.conf file could be tagged by a rank (default: 0), and
> the highest (-rank, version, revision) should have the precedence.
>
> -- 
> Vincent Lefèvre <vincent at vinc17.org> - Web: <http://www.vinc17.org/>
> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/ 
> blog/>
> Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS- 
> Lyon)
> _______________________________________________
> macports-dev mailing list
> macports-dev at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo/macports-dev


Randall Wood
rhwood at mac.com

"The rules are simple: The ball is round. The game lasts 90 minutes.  
All the
rest is just philosophy."