Subject: Re: New p5 Date-Calc package questions.
To: None <hubert.feyrer@informatik.fh-regensburg.de>
From: Simon Burge <simonb@NetBSD.ORG>
List: tech-pkg
Date: 12/23/1999 09:39:45
Hubert Feyrer wrote:

> On Mon, 20 Dec 1999, Simon Burge wrote:
> > Part of the problem is that I don't think we'd know what all the perl
> > `categories' are in advance, so this list could be ever changing.
> 
> Well, we do know, as we need to work on each p5-* pkg. 

As Christoph Badura noted:

> No, we do *NOT* know in advance.  Any number of Perl packages can be added to
> the package system after the perl package itself is installed.

(back to Hubert's email):

> > Perhaps best for now would be:
> > 
> > 	@unexec rm -r %D/lib/perl5/site_perl/${MACHINE_ARCH}-${LOWER_OPSYS}/auto
> > 
> > somewhere in lang/perl5's PLIST-mi.
> 
> And not list the file in any of the other PLISTs, ok.

I'll check this and fix any that I find.

> > Cool - there's about a dozen other p5 packages that use the "ugly"
> > construct.  Shall I change those?  The www/p5-libwww case it a bit
> > ugly though, and looks like it will need some sed'ing either way...
> 
> Maybe ask the maintainers first... I wouldn't mind shaving off a few
> cycles. 

Will do.

> > > Something else:
> > > Perl does not support shared objects etc. on all our archs, and thus the
> > > .so and .bs file will not be there. Example archs are (I think) pmax and
> > > alpha (don't ask that's perl...). See e.g. security/p5-MD5 for a
> > > workaround using different PLISTs. 
> > 
> > Yuck!  I'll do this for my package for now.
> > 
> > Hmm, both pmax and alpha are ok - maybe it might be time to deprecate
> > non shared support.  I wonder about pc532, vax, perhaps powerpc...
> 
> Please note that the decision whether to use PLIST-md.shared or
> PLIST-md.static is used is fixed in bsd.pkg.mk. I think if your PLIST
> works on pmax and alpha as well, we should leave it the way it is.
> 
> PLIST-m* is an ugly hack anyways.

It looks like it's only if NOPIC is defined that PLIST-md.shared is
used.  I guess it's conceivable that someone may not want shared
libraries in /usr/pkg (_and_ that all packages do the right thing
anyway).  Is there any rational use for this at all?  Methinks it's
time to remove the PLIST-m* unless there's any good objections.

Alistair, others - are these used on non NetBSD platforms?

Simon.