Date: Sun, 25 Nov 2001 17:10:28 -0500 From: Pete Fritchman <petef@databits.net> To: Anthony Kim <niceshorts@yahoo.com> Cc: ports@freebsd.org Subject: Re: Port of OpenCA pending... Message-ID: <20011125171028.D91717@databits.net> In-Reply-To: <20011125185355.88931.qmail@web12805.mail.yahoo.com>; from niceshorts@yahoo.com on Sun, Nov 25, 2001 at 10:53:55AM -0800 References: <20011125185355.88931.qmail@web12805.mail.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
| Hi
|
| I hope to contribute to the Project by creating a port for
| OpenCA. I've gotten most of the ports done. Here's my planned
| list to be added to ports/security
Cool. :)
| Question#1:
|
| In pkg-plist, is it ok if I not include the parent directory
| (OpenCA below) in case the user decides to uninstall and
| reinstall one of the several p5-OpenCA* modules? Otherwise, if
| you make deinstall one module, you would blow away all the other
| OpenCA modules.
|
| pkg-plist example:
|
| lib/perl5/site_perl/%%PERL_VER%%/%%PERL_ARCH%%/auto/OpenCA/REQ/.packlist
| lib/perl5/site_perl/%%PERL_VER%%/OpenCA/REQ.pm
Since %%PERL_ARCH%% is always going to start with a lowercase letter,
I'd switch these two lines (to keep the plist sorted).
| @dirrm lib/perl5/site_perl/%%PERL_VER%%/%%PERL_ARCH%%/auto/OpenCA/REQ
You'd want to add:
@unexec rmdir %D/lib/perl5/site_perl/%%PERL_VER%%/%%PERL_ARCH%%/auto/OpenCA 2>/dev/null || true
@unexec rmdir %D/lib/perl5/site_perl/%%PERL_VER%%/OpenCA 2>/dev/null || true
This basically attempts to remove the directory, and if there's still
things in it from other p5-OpenCA* ports, it will not fail. This is how
all the other Perl ports do it.
| Question#2:
|
| Several of the p5-OpenCA modules include a testing script,
| prova.pl . However, Perl installs them all to the same location:
| lib/perl5/site_perl/%%PERL_VER%%/OpenCA/prova.pl
|
| Do you think its okay to pretty much ignore prova.pl? (Easiest)
No - if the port installs extra files that are not in the pkg-plist,
this is bad for two reasons:
(1) The FreeBSD ports build cluster will not generate a package
(because it will detect this omission from the packing list)
(2) If a user installs the port, and later on decides to deinstall it,
there will be cruft left over.
| Or should I patch Makefile to install prova.pl under OpenCA/MODNAME/
| instead and subsequently include prova.pl in pkg-plist?
Up to you I guess. Do you think the "prova.pl" testing scripts are
really necessary? If so, maybe a more suitable place for these scripts
would be ${PREFIX}/share/examples/OpenCA/${PORTNAME}. (And you could
use the same @unexec rmdir ... magic to remove
${PREFIX}/share/examples/OpenCA in the pkg-plist)
| Remark about modules:
|
| OpenCA distribution includes each of the p5-OpenCA modules under
| src/modules/ - my thinking is that we'd want a port for each
| module to handle changes better - and so that sysutils such as
| pkgdb won't complain. Do you think that strategy is valid?
Yep -- I don't see any reason to group them together, and I agree you it
would be easier to manage (both in the ports tree and an installation).
-pete
--
Pete Fritchman [petef@(databits.net|freebsd.org|csh.rit.edu)]
finger petef@databits.net for PGP key
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011125171028.D91717>