Great notice, i am glad as old Svr4 admin, other that doing part of rpm5. Best regards
From: Sriram Narayanan
Sent: 05/11/2010, 19:05
Subject: Fwd: Proposal: use rpm5 package format and the smart package manager
Here's the latest on Belenix using rpm5 :)
---------- Forwarded message ----------
From: Sriram Narayanan <email@example.com>
Date: Fri, Nov 5, 2010 at 9:07 PM
Subject: Proposal: use rpm5 package format and the smart package manager
To: Belenix Discuss <firstname.lastname@example.org>
I want to propose that we move to rpm5 to give the user the following
- easy to use smart package manager (using yum and rpm is optional)
- the familiar rpm format for the actual package files
- support from the rpm5 and the smart package manager community
Reasons for rpm5:
- based wide spread use on desktop as well as server grade Linux based
distros such as RHEL, rpm works well and meets our needs of a good
modern package system
- I have managed to build rpm5 and have requested Jeff Johnson, the
present rpm5 maintainer and developer, to integrate two fixes needed
to build rpm5 on the opensolaris platform
- the current maintainers of rpm5 have given us a go ahead on bundling
rpm5 with Belenix 
- rpm5 is actively maintained 
- it uses modern compression systems and libraries 
- it is used by other distributions as well, who don't mind sharing
their learning with us 
1. Compatibiity with pkg-build spec files
We could potentially directly consume all the pkg-build specific spec
files in case we want to attempt source builds. I'm fairly confident
this should work, and I will be working on a test case. This may very
well be needed in case we use gcc to build KDE packages (necessary in
case we don't use hajma's SS12 built KDE IPS packages).
2. Direct import of IPS files into rpm5 files.
In case we decide to convert openindiana packages into rpm packages,
we'll need something like alien which would read IPS and generate rpm
files. This needs some investigation.
I also propose that we use the smart package manager
- There are a number of dependency resolution issues that the smart
package manager has solved 
- There are a number of interesting features 
- There is wide spread adoption today of this tool by Ubuntu, Fedora,
and Suse, and other efforts such as unitylinux.
- smart provides many of the convenient command line parameters as does apt-get
- the smart community members are OK with us bundling smart within Belenix 
- Here is the smart package manager FAQ 
Unfortunate reasons for not being able to use .deb files (the dpkg format)
- At this time, the debian-legal community is still largely against of
bundling Nexenta's zfs-aware dpkg with a distro. 
- We don't have either the mental energy, the time, of the legal
awareness to go argue with debian-legal
- we don't want to get into disagreements with other open source and
free software communities.
Some thoughts on questions about apt-get
1. apt-get is great !
apt-get is a front for dpkg. The convenience of apt-get is matched by
the smart package manager.
2. apt-get gives me everything
Actually, apt-get merely queries a catalog of software, and let's us
install, upgrade and remove software. A rich collection of software
packages is something that the overall openindiana community can work
together on (with Belenix being part of that community).
3. apt-get is easy to use
Well, rpm has similar commands, and so does smart. Our overall
emphasis should be on using the smart package manager which will
consume rpm files underneath.
RPM Package Manager http://rpm5.org
User Communication List email@example.com
Received on Fri Nov 5 19:42:29 2010