> their own design (but I should add that Portage > provides a tool for > converting to the Solaris package standard).
Eric, would you know who implemented this? AFAIK, portage did tbz2 and rpm. I am trying to do updates to pkg database to make pkgadd and family aware of portage installs. And if its already there that will save me a lot of time. For the bigger picture, I propose that all packaging systems agree on naming conventions for packages. Currently, blastwave packages are CSW prefixed, sun pkgs are SUNW prefixed. If we all use the same packaging name, and export --prefix, --include, --lib paths thru pkg-config "like" interface, then I can have some packages installed from sun, some from portage and others from blastwave. Every mechanism uses/updates the same backend(solaris package) so, every mechanism is aware of the fact that a package PKGlibiconv exists, although it was installed by portage, and it will not try to install its own version if the existing version meets the version requirements. Similarly, portage knows that PKGcoreutils is present although it is a SUNW package and it will not try to install its own coreutils. Similarly, pkgadd knows that PKGgtk+2 is present although it was installed from blastwave, and will not try to install its own when updating PKGmetacity. This idea is very futuristic and will require some effort but we definitely need to merge portage and pkgadd in such a way because it messes with zones otherwise. This message posted from opensolaris.org _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
