Subject: Re: Adding extra directories to pkgsrc
To: Hauke Fath <hf@spg.tu-darmstadt.de>
From: D'Arcy J.M. Cain <darcy@NetBSD.org>
List: tech-pkg
Date: 02/24/2005 09:05:37
On Thu, 24 Feb 2005 14:27:09 +0100
Hauke Fath <hf@spg.tu-darmstadt.de> wrote:
> Am 24.02.2005 um 7:39 Uhr -0500 schrieb D'Arcy J.M. Cain:
> >1. Add a .cvsignore entry to the mid level pkgsrc tree for wip.
> >2. Add a local directory with a gloable .cvsignore entry like
> >distfiles does.
> >
> >Does anyone see a problem with those changes?
> 
> "Why?"
> 
> 1. breaks when you decide to call your wip sandbox 'wip-20050401'.

Well, it doesn't break.  It just does what bare "wip" does now.

> 2. means local/wip/foo is one level deeper than shells/tcsh which 
> breaks relative .includes in wip/* Makefiles.

I may not have been clear.  These two proposals are unrelated.  The wip
one is to allow people to add wip at the same level as other categories
without it complaining about unknown directories.  The local one is
about adding another directory, also at the category level, to give
people a place to add their own local packages, possibly including their
own local meta packages, again without it complaining about unknown
directories.

> The 'wip?' output from a 'cvs -q update' tells me there are 
> directories around that the current cvs run dies not descend into. I 
> like that.

OK, nothing stops you from calling it wip-20050401 or my-wip or whatever
to get that behaviour.  On the other hand, some people like having cron
scripts that only send email if there is a problem.  With my proposal
they can filter out normal updates and only get output if there are
things they need to deal with.

It's not a big deal to work around this in any case.  I just saw that we
do this for distfiles already and thought that it was a reasonable
extension.

-- 
D'Arcy J.M. Cain <darcy@NetBSD.org>
http://www.NetBSD.org/