Package: module-assistant Followup-For: Bug #402811 Hi Ken,
thanks for your work on this. For those of us who upload m-a generated module packages to a local apt repository, an epoch will be confusing and not really add any recognition value. For example, to stay with kqemu, my users might see the following availabe versions in aptitude: 2.6.25+1.3.0~pre11-1 1:2.6.25+1.3.0~pre10 While it's clear that the epoch one is higher and the preferred one, it's confusing as to why this is. I propose that you do not implement the epoch, and instead put an additional string between the kernel version and the module source version, for example like so: <kernelversion>+modass+<modulesourceversion> Verification: $ dpkg --compare-versions 2.6.25+1.3.0~pre11-1 '<<' 2.6.25+modass+1.3.0~pre10 && echo yes yes Another possibility: $ dpkg --compare-versions 2.6.25+1.3.0~pre11-1 '<<' 2.6.25.modass+1.3.0~pre10 && echo yes yes Both options would make it clear that this is a m-a built package, give this package a higher priority than linux-modules-* supplied packages, and avoid introducing an epoch. Thank you for your consideration. Ciao, Philipp PS: incidentially, something like "2.6.25+m-a+1.3.0~pre10" would also work, but of course is very very wrong if there's not also a debian revision appended. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]