ntfs-3g and ntfsprogs merge

Elan Ruusamäe glen at pld-linux.org
Thu Apr 21 19:39:18 CEST 2011


On 21.04.2011 12:22, Bartosz Taudul wrote:
> On Thu, Apr 21, 2011 at 10:50 AM, Caleb Maclennan<caleb at pld-linux.org>  wrote:
>> Yes, the Provides and Obsoletes will take care of being able to
>> upgrade and replace the previous package names. The problem is that
>> there is no notification feature for the OLD packages, they just get
>> stuck at an old version and eventual disappear from the stable package
>> set. However this is not a unique problem to this issue, it happens
>> regularly and even I have been known to ask on this list where to find
>> the "new" package name for something project that morphed into
>> something else.
> Maybe we should provide empty rpms for the obsoleted packages with the
> appropriate R: and some special name in release field? For example:
> ntfs-3g-1.2.3-69.packageexpired, R: ntfs3g-newshit
>
> Then we may have a simple cron job that would do rpm -e `rpm -qa|grep
> packageexpired` on a regular basis to remove the obsolete stuff.
>
> wolf
id prefer keeping original package names, even in built from different src.rpm.spec

-n ntfsprogs
-n ntfs-3g


or they are not separateable anymore (can't think of ntfs-3g for mount 
tools and ntfsprgs as  fsck tools?)

-- 
glen



More information about the pld-devel-en mailing list