[nycbug-talk] creating "local" ports
Brian A. Seklecki
lavalamp at spiritual-machines.org
Fri Nov 3 22:32:56 EST 2006
In Pkgsrc we have pkgsrc-wip which essential provide the mechanism you're
The problem becomes modifications to existing ports where reanaming the
PKGNAME will essentially break dependencies and portupgrade logic.
On the other than -- with NetBSD, and vanilla CVS for updates, we don't
have to worry about CVSUp blow about localizations.
On Fri, 3 Nov 2006, Charles Sprickman wrote:
> Top post alert...
> Brought over to -ports list:
> (screwed up the subject, was editing/forwarding)
> I'm kind of surprised there isn't a mechanism to easily manage a local
> ports category. I've been getting pretty compulsive about trying to keep
> everything I can in ports so I have a clear picture of what's installed on
> each box.
> On Fri, 3 Nov 2006, Sujit Karataparambil wrote:
>>> I'd like to copy these into some sort of local ports directory, but that
>>> a few questions:
>>> -Is there an accepted location for this branch, ie: /usr/ports/local that
>>> not get blown away on a cvsup or portsnap update?
>> There is an LocalBase Port Location in FreeBSD.
>> -How does one handle packages that depend on say, qmail, but I now want to
>>> depend on local-qmail? I know portupgrade can be tought this by setting
>>> alternate pkgdep, but is there any clever way of doing this so that when
>>> not using portupgrade the deps are adjusted?
>> Hope this might Help.
> % NYC*BUG talk mailing list
> %Be sure to check out our Jobs and NYCBUG-announce lists
> %We meet the first Wednesday of the month
-lava (Brian A. Seklecki - Pittsburgh, PA, USA)
"...from back in the heady days when "helpdesk" meant nothing, "diskquota"
meant everything, and lives could be bought and sold for a couple of pages
of laser printout - and frequently were."
More information about the talk