-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Richard Bos wrote:
Pascal,
Op maandag 19 december 2005 10:19, schreef Pascal Bleser:
Another idea... let's call it "meta" or "virtual" packages...
Make empty packages that pull several dependencies using their Requires tags to make packagers' life easier.
this is nothing new. It has been used in suse-7.3 already. This following packages are virual ones: ./suse/extra/8.1/koffice-suite-3.0-0_rb1.i386.rpm ./suse/extra/7.3/gnome2-2.0-rb2.i386.rpm ./suse/extra/7.3/kde-3.0-3.i386.rpm ./suse/extra/8.2/MPlayer-suite-1.0-rb2.i586.rpm
You find them in ftp://ftp.gwdg.de/pub/linux/misc/apt4rpm/
Sure, I could also just roll my own in my own repository, but the point is to have them in the core distribution. And with any package manager frontend, not only apt. If it's only in one additional repository (and furthermore only with apt), it's not sufficient. If someone wants to rebuild my src.rpm, she won't be able to find that virtual package unless she 1) has and uses apt 2) has configured apt to include that repository IMO src.rpm's should really be "rebuildable" out-of-the-box, not only under certain conditions and requiring to use specific repositories (besides the core distribution or what would be needed for the BuildRequires (e.g. packman)), as well as requiring specific package manager frontends. Same is true for the tools BTW, src.rpm's must be "buildable" just with rpmbuild.
Mauricio "netmask" Teixeira and I talked about that idea, as Mauricio told me that Connectiva has that approach with so-called "task" packages (task-c++-devel, etc...). They also use it to do the same as SUSE Linux' "selections" (*.sel files in yast2 repositories), e.g. "task-mail-server", but that's a different story ;)
I could really use such a "meta-gnome-devel" package ;)))
Than use apt:
apt showgroup ...
Very interesting, but not of any help in this case, because it only works with apt and when you have
that repository configured.
cheers
- --
-o) Pascal Bleser http://linux01.gwdg.de/~pbleser/
/\\