What is the proper way to maintain a local port file?

[Bjarne D Mathiesen]

Michael_google gmail_Gersten wrote:
> What is the proper way to maintain a local port?
> 
> There are two cases that I'm looking at:
> 
> 1. Creating a new port for a program that does not currently have a port.

there's only one solution here:
running a local depository
the guide has instructions for that:
http://guide.macports.org/#development.local-repositories

> 2. Modifying an existing port.

2 solutions:
1) as above - moving the port to your local depository
2) keeping local patches
(2) can be a bit of a pain in the ass, but has the advantage that you'll
discover when and if the official port breaks your patch. With (1) your
local repository takes precedense over the official ports repository.
This has the consequense that all responsibility for mantaining the port
is now completely on your shoulders.

I've got procedures and scripts to handle both cases that you are
welcome to get and take a look at :-)

> 
> For 2, the specific case I'm looking at is qemu -- I only need the 386
> emulator, and do not need to build the other 3 that are built by
> default (and apparently have no way to turn off).
> 
> The "ideal" method as I see it, based on very limited knowledge of
> what's involved, would be to edit a port file, store both the original
> and my modification, and on update of the portfile trigger a "you must
> inspect this portfile" warning, and show how my patches will fit into
> the new portfile.
> 
> For 1, there could be any number of things that do not have a port yet
> that I'd want to create and test a port for, before submitting.


-- 
Bjarne D Mathiesen
København N ; Danmark ; Europa
----------------------------------------------------------------------
denne besked er skrevet i et totalt M$-frit miljø
MacOS X 10.6.7 Snow Leopard ; 2.8GHz Intel Core i7 ; 16GB 1067MHz DDR3
                                       http://webadmin.mathiesen.info/