On Tuesday 2011-09-20 23:10, Greg Freemyer wrote:
obsoletes/provides relation: Obsoletes: foo < %version Provides: foo = %version
I've got a project that may need this.
== background == I am working with the next4 team and they have a ext4dev patch[...] My need. To go with the above module, e2fsprogs has to be extended to have the legacy programs mkfs.ext4dev, fsck.ext4dev, etc. handle this new definition of ext4dev (ext4dev is unused since the 2.6.29 kernel I think).
Yeah perhaps one should not call the effort 'ext4dev' but maybe 'ext4 with snapshots' :-)
My issue is in the packaging. I doubt I should submit a patch to update the core e2fsprogs package, so I was thinking of creating a e2fsprogs-ext4dev package. [...] handling the package name, provides, and obsoletes logic?
By using Obsoletes/Provides in this case, you enact zypper to automatically select your package during dependency resolution of another package's dependencies (say, perl-Bootloader). This of course is undesired, since your package contains components that are considered "fragile" by your very own definition. IOW, no Obsoletes/Provides for your case. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org