cvs commit: ports/x11/kdebase3 Makefile pkg-message ports/x11/kdebase3/files pkg-message

[David O'Brien]

On Sun, May 02, 2004 at 07:32:29PM +0200, Michael Nottebrock wrote:
> > >   Reported by: obrien
> >
> > Thank you for fixing this, but why didn't you just leave pkg-message
> > where it was?  Just because it needs fixing up it doesn't have to live in
> > the non-standard files/ directory.  Please consider moving that and the
> > plists back to the main kdebase3 directory.
> 
> I don't think a pkg-message that really isn't one but a template that
> needs to be processed first should be visible, so I'd rather hide it in
> ${FILESDIR}.  Perhaps I should have renamed it to message-template?
> Also, our plist bits aren't standard plists (the real plist is
> concatenated from them, depending on build options) and thus don't
> belong into the portdir, but into ${FILESDIR}.

I TOTALLY disagree with this hiding these standard files in ${FILESDIR}.
I've been here 10 years and haven't heard of this as a general rule to
follow.  It certainly isn't documented in the Porter's Handbook.

Look at editors/vim, lang/gcc3[1234], astro/xplanet, audio/fmio,
biology/distribfold, databases/py-MySQL, devel/cvsweb, devel/perforce,
mail/cyrus-imapd, net/samba, sysutils/webmin, textproc/aspell,
extproc/ispell, www/squid, x11/xscreensaver, (total of 133 ports)
for examples of ports that tweak, modify and/or add major content to
${TMPPLIST} at build-time.

Same for pkg-message.  See astro/setiathome/Makefile as a correct
example.

Obfuscating standard ports files does not benefit users and makes the
Ports Collection harder to use than it needs to be.
 
-- 
-- David  (obrien at FreeBSD.org)