On Oct 6, 2012, at 01:38, MacPorts <[email protected]> wrote: > Page "howto/PatchLocal" was changed by [email protected] > Diff URL: > <https://trac.macports.org/wiki/howto/PatchLocal?action=diff&version=3> > Revision 3 > Comment: Incorporated changes from Rainer Müller > Changes: > -------8<------8<------8<------8<------8<------8<------8<------8<-------- > Index: howto/PatchLocal > ========================================================================= > --- howto/PatchLocal (version: 2) > +++ howto/PatchLocal (version: 3) > @@ -11,46 +11,64 @@ > > == Installation == > > -=== Step 1: '''Get your port's sourcecode''' === > +=== Step 1: '''Set up a local repository''' === > + > +If you want to make changes that stick and won't be overwritten by accident, > you need to set up a local > +repository, described in full here: > http://guide.macports.org/#development.local-repositories > + > +Do this to create a new Port (as root): > +{{{ > +umask 022 > +mkdir -p /usr/local/ports/ > +cd /usr/local/ports > +cp -r `port dir arb` . > +mv arb arb-devel > +}}} > + > +Add this line before the 'rsync://.......' line in > /opt/local/etc/macports/sources.conf, at the end of the file: > +{{{ > +file:///usr/local/ports > +}}}
We should not be suggesting that users put ports in /usr/local/ports. Although doing so won't cause any problems, installing libraries in /usr/local/lib or headers in /usr/local/include does, and therefore our standing policy is to not support users installing files in /usr/local, and in the course of troubleshooting we often advise users to rename or remove /usr/local. Almost any parent directory other than /usr/local would be a better choice. _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo/macports-dev
