I am not sure whether openpkg-tool is simply missing some deps or whether I am completely mistaken about the principle of OpenPKG.
On a clean, small install of solaris9 + binary openpkg*.sh (+ the basics like rsync/bash/...) I built opnpkg-tool-1.2.2. This machine is supposed to become my OpenPKG RPM server. First try: ---------------- [openpkg] index -p solaris-2.9 -C /cw/share/rpm-cache.db -o ./PRIV-INDEX.rdf -i /export/openpkg/BIN/ Can't locate DB_File.pm in @INC (@INC contains: /usr/perl5/5.6.1/lib/sun4-solaris-64int /usr/perl5/5.6.1/lib /usr/perl5/site_perl/5.6.1/sun4-solaris-64int /usr/perl5/site_perl/5.6.1 /usr/perl5/site_perl /usr/perl5/vendor_perl/5.6.1/sun4-solaris-64int /usr/perl5/vendor_perl/5.6.1 /usr/perl5/vendor_perl .) at /cw/lib/openpkg/openpkg-index.pl line 942. ---------------- I then installed openpkg's perl (plus gcc, binutils) and got: ---------------- [openpkg] index -p solaris-2.9 -C /cw/share/rpm-cache.db -o ./PRIV-INDEX.rdf -i /export/openpkg/BIN/ Can't locate DB_File.pm in @INC (@INC contains: /cw/lib/perl/5.8.0/sun4-solaris /cw/lib/perl/5.8.0 /cw/lib/perl/site_perl/5.8.0/sun4-solaris /cw/lib/perl/site_perl/5.8.0 /cw/lib/perl/site_perl .) at /cw/lib/openpkg/openpkg-index.pl line 942. ---------------- After installing perl-db-1.2.0 (and its dep db-4.1.25.0-1.2.0) everything's fine. This leads my to a few fundamental questions: 1. Am I the only one trying to build minimal installs? My boxes will be production and staging servers on the Internet. Less software -> less frequent holes, less frequent patching, less downtime, less work. 2. Am I the only one trying to work with a central build system and BINARY ONLY machines? That is NO rebuilding of RPMs on production machines? My logic here: Centrally built Binaries -> guaranteed release synchronicity between staging/production -> fewer problems to be debugged. 3. Maybe I am not yet understanding the scope of "self contained"? I'd guess that an openpkg-tool that needs perl would insist in using perl from openpkg. (if so, it's lacking "Requires: perl, perl-db"). If it's ok to use "Solaris perl", that's fine with me (but probably calling for tons of compatibility problems), then OpenPKG should enhance the dep mechanism to check for host os libs/modules/the lot (DB_File.pm) in this case. Sorry for the longish post, but I am beginning to fear that I either picked the wrong tool for the job - or more probably that I got the underlying principle wrong. Please enlighten me;-) Thanks, IngoTee ______________________________________________________________________ The OpenPKG Project www.openpkg.org Developer Communication List [EMAIL PROTECTED]
