On Fri, Feb 25, 2011 at 4:06 AM, Joerg Schilling <[email protected]> wrote: [...]>> I will be partly following the new naming scheme in IPS. I will >> not use hierarchical names as they are too verbose and difficult >> to remember. Just the last component which is the actual package >> name. RPM's grouping/categorization is fine. > > So I asume that you did create the rpm spec files manually? >
Yes, only for the packages that I intend to build from source. > I did create the SVR4 packages (the changes and new packages since build 135) > manually. There are currently 270 files left overt that need to be introduced > into existing packages. > > Regarding the naming scheme, I did introduce a new tag in the pkginfo file > that > follows the IPS naming scheme: > > SUNWinstall-beadmr/pkginfo.tmpl: > > PKG=SUNWinstall-beadmr > SCHILY_PKGNAME="install/beadm@PKGVERS:TIME" > SCHILY_OLDNAME="SUNWbeadmr" > NAME="beadm utility (Root)" > ARCH="ISA" > VERSION="ONVERS,REV=0.0.0" > > translates into: > > SUNWinstall-beadmr/pkginfo: > > PKG=SUNWinstall-beadmr > SCHILY_PKGNAME="install/[email protected],5.11-0.148:20110224T151211Z" > SCHILY_OLDNAME="SUNWbeadmr" > NAME="beadm utility (Root)" > ARCH="i386" > VERSION="11.11,REV=2011.02.24.16.12" > > and there is > SUNWbeadmr/pkginfo.tmpl: > > PKG=SUNWbeadmr > SCHILY_NEWNAME="SUNWinstall-beadmr" > NAME="beadm utility (Root)" > ARCH="ISA" > VERSION="ONVERS,REV=0.0.0" > SUNW_PRODNAME="SunOS" > SUNW_PRODVERS="RELEASE/VERSION" > > with a back pointer to the new SVR4 package name. > > There is a script "pkgsort" that automatically creates a list with package > names in the needed install order (pkgsort takes 7 seconds to finish). > > see: > http://hg.berlios.de/repos/schillix-on/file/0fd93319a782/usr/src/pkgdefs/pkgsort > > and there is "pkginstall" that installs all Schillix-ON packages in 50 > seconds: > > http://hg.berlios.de/repos/schillix-on/file/0fd93319a782/usr/src/pkgdefs/pkginstall > > I will later introduce a wrapper that allows to work based on the IPS package > names. > I followed a similar mechanism using the earlier transactional Python based package manager I had developed earlier for BeleniX on top of SVR4 packaging: http://belenix.svn.sourceforge.net/viewvc/belenix/trunk/spec_files/ext-sources/spkg?revision=175&view=markup http://belenix.svn.sourceforge.net/viewvc/belenix/trunk/spec_files/ext-sources/spkg_mod.py?revision=395&view=markup http://belenix.svn.sourceforge.net/viewvc/belenix/trunk/spec_files/ext-sources/spkg_trans.py?revision=189&view=markup http://belenix.svn.sourceforge.net/viewvc/belenix/trunk/spec_files/ext-sources/tsort.py?revision=150&view=markup The last one is a Python based topological sort that takes approx a second to sort 850 packages. Including the time taken to actually build the partially ordered map it is probably around 5 seconds in total. One problem with SVR4 is that it does not have the concept of an "upgrade". If I deliver a new version of a package and overwrite the older one, it just adds or overwrites all the files. If some file pathnames have changed it does not automatically remove the older pathname. So both file locations remain. In addition the latest SVR4 seems to have a subtle bug. In livecd mode if I mount the harddisk and try to remove a package using pkgrm -R <mntpt> it crashes somewhere in libspmi. I did not have the time or patience to fully debug it so I used a slightly older version in BeleniX. Regards, Moinak. -- ================================ http://www.belenix.org/ http://moinakg.wordpress.com/ _______________________________________________ belenix-discuss mailing list http://mail.opensolaris.org/mailman/listinfo/belenix-discuss http://groups.google.com/group/belenix-discuss
