cvs commit: ports/misc/alevt Makefile pkg-descr pkg-plist

[Alexey Dokuchaev]

On Thu, May 26, 2005 at 02:01:27PM +0200, Pav Lucistnik wrote:
> Alexey Dokuchaev p??e v ?t 26. 05. 2005 v 11:49 +0000:
> > On Thu, May 26, 2005 at 01:35:43PM +0200, Pav Lucistnik wrote:
> > > Alexey Dokuchaev p??e v ?t 26. 05. 2005 v 11:33 +0000:
> > > > On Thu, May 26, 2005 at 01:29:18PM +0200, Pav Lucistnik wrote:
> > > > > Alexey Dokuchaev p??e v ?t 26. 05. 2005 v 10:51 +0000:
> > > > > > danfe       2005-05-26 10:51:13 UTC
> > > > > > 
> > > > > >   FreeBSD ports repository
> > > > > > 
> > > > > >   Modified files:
> > > > > >     misc/alevt           Makefile pkg-descr pkg-plist 
> > > > > >   Log:
> > > > > 
> > > > > >   - Mute directory creation in do-install: target
> > > > > 
> > > > > Why? It's nothing filthy to print mkdir, and at least one know what's
> > > > > going on. I was un-muting mkdir's all over the place last year, myself.
> > > > 
> > > > Most ports still mute it, from what I can tell.  I think that it's reasonable
> > > > enough, just like we don't get CVS commit notifications when create/chechin
> > > > directories.
> > > > 
> > > > Still, if I get a feeling that this disturbs people a lot, I will revert this change.
> > > > FWIW, we should explicitly set policy on things like that in Porters' Handbook.
> > > 
> > > Oh no, not another policy! I consider it a matter of style and I was
> > > curious about your motivation on this change.
> > 
> > :-)
> > 
> > Pav, it might be excessive perfectionism, but currently our Ports Collection,
> > despite its great functional state, it not very consistent with respect to knobs
> > handling/names, indentation, and general mark-up.  And I kinda fail to see why you
> > don't like policies so badly.
> 
> Policies take fun out of work. You can't get much creative.

But policies (or should I use your words, "best practices") can be different.  I
doubt that having a rule on how to create directories can steal fun of creating new
and improving existing ports from you.  :-)

> 
> > BTW, I agree with your "matter of style" assessment, but the fact that FreeBSD
> > code is so better style(9)-consistent than, say, Linux, is one of the things I
> > love it for.  IMHO, "stylificaion/consistensyfication" of our Ports tree is a
> > decent goal to follow, while being low-priority one, indeed.
> 
> I'd much rather see a best practice document than a rigid policy on
> issues of style.

Well, I tend to agree.

./danfe