package, package2, package3 naming-with-version exploit

Jan Zelený jzeleny at redhat.com
Fri Mar 29 13:38:44 UTC 2013


On 29. 3. 2013 at 13:48:21, Jan Zelený wrote:
> On 29. 3. 2013 at 12:37:18, Richard W.M. Jones wrote:
> > On Fri, Mar 29, 2013 at 01:15:53PM +0100, Jan Zelený wrote:
> > > Example:
> > > python-3.2.3-7.fc17       (metapackage)
> > > python2-2.7.3-7.2.fc17
> > > python3-3.2.3-7.fc17
> > > 
> > > Metapackage "python" could be pointing to whatever version the
> > > maintainer
> > > thinks is the best, obviously the version of the metapackage would
> > > correspond with the version of package it points to. Update path is
> > > clearly defined and user can do both "yum install python" and "yum
> > > update
> > > python" without any confusion.
> > 
> > Couldn't it be done even more easily by having only the python3
> > package "Provides: python"?
> 
> Yeah, probably. But that wouldn't show up on "yum list python". Not sure if
> that is actually a big issue ...

Ah, I just remembered another issue. When using this provide it would be 
difficult to specify that other-than-the-latest version should be installed as 
default.

Therefore the metapackage still seems to be the best option.

Thanks
Jan


More information about the devel mailing list