packaging rules

Patryk Zawadzki patrys at
Wed Aug 8 13:55:11 CEST 2007

On 8/7/07, Jakub Bogusz <qboosh at> wrote:
> On Fri, Aug 03, 2007 at 06:48:09PM +0200, Patryk Zawadzki wrote:
> > So, is there anything against using feature-provides and conflicts
> > (only for really conflicting packages)?
> >
> > Old packages should not be a problem if we rebuild all affected software.
> It is a problem as just rebuilding them don't force installing them on all
> existing machines. In such cases I propose changing package name Obsoletes
> to Conflicts: package-name < (E:V-R before Provides has been added).
> Also, you found a set of packages which are really mutually exclusive
> and installing more than one makes no sense: issue*. Just dropping
> Obsoletes makes an unresolved conflict in distribution (try poldek
> --verify=fileconflicts). I think P+O: issue-package (literally, virtual
> package with that name) is the way to go (keeping in mind previous
> paragraph).

Added versioned Conflicts where possible. Can't add C: issue < 2.99-2
as they were and are all providing "issue."

I could drop the provide but I'm not sure if anything requires or
required that in Ac/Th.

Patryk Zawadzki
Generated Content

More information about the pld-devel-en mailing list