[packman] packman future
Manfred Tremmel
Manfred.Tremmel at iiv.de
Fri Jan 10 19:28:20 CET 2003
Am Donnerstag, 9. Januar 2003 19:10 schrieb Waldemar Brodkorb:
> #Packman-Depends: xine-lib xine-ui
Good idea, but I see problems. For example, I have one xine-lib, because
it works with all SuSE-versions from 7.1 up to 8.1, but I have to
xine-ui Packages one for SuSE 8.1 and one for SuSE 7.1 to 8.0.
Can you imagin how this can be automaticly solved? There is a libxine
i686 for SuSE 8.1 and one ppc-package for SuSE 7.3, what5 dependencies
would be set? The same Problem with i386, i486, i586 and i686 packages.
I don't want to have the precessor-architecture or SuSE-versions in the
specfile, because I don't want to have more specfiles. In the moment I
have three xine-ui and three xine-lib specfiles to take care for (the
official for the cvs-compiles [packman-style] and one for the releases
[packman-style]).
And simply dependencies you can get with 'rpm -qpR <RPM-File>',
description with, the rest with 'rpm -qpi <RPM-File>', 'LC_ALL=en rpm
-qpi <RPM-File>', ...
> #Packman-Info-de: asfsaf
> #Packman-Info-en: adasf
Ähm, can we do this rpm like:
#Packman-Info
#Packman-Info -l de
But, do we need it? General package info is not a good thing, to have in
the spec-file, there can be a lot of versions (different SuSE-Versions,
different cpu-architectures, ...). I would do this in a Web-Interface
like it is done now.
--
Machs gut | http://www.iivs.de/schwinde/buerger/tremmel/
Manfred | http://packman.links2linux.de/
More information about the Packman
mailing list