ticket#25375 couchdb (rookie here)

[Scott Webster]

On Fri, Jul 2, 2010 at 12:32 AM, Scott Haneda <talklists at newgeo.com> wrote:
>
> Won't that get written over possibly on the next `port upgrade` is ran?
>

I would imagine it would be overwritten when you selfupdate or sync,
yes.  But as long as you don't rebuild the port it should keep
working.

> For the OP (Daniel T.)
> When I have had to go down this road I would set up my own local repository.
>
>    http://guide.macports.org/#development.local-repositories
>
> This was one of the very first things I did when I first came to MacPorts.  I was pretty rookie myself, and still am :) so this could be totally off base since I have not been following this thread too closely.
>
> Whenever I have had to apply a patch or use other files, I work in ~/macports, which is where I decided I was going to setup my local repository.  I then create the correct sub directory for the category, in this case, 'databases' and within that I would either make the 'counddb' directory and the 'files' directory within ( ~/macports/databases/counddb/files ), or, if it was a modification of an existing port, I would use `port dir portname` to locate the orginal port, and copy it into my local repository.
>

I've been doing this too, but I was always renaming my local ports so
they wouldn't conflict with the "master" version.  But reading the
guide again it seems that it just takes the order from sources.conf,
which is convenient.

Scott