Am Montag, 3. November 2003, 12:32:58 Uhr MET, schrieb [EMAIL PROTECTED]:
> I did start naming everyting <version>.92mdk to distinguish them from
> cooker stuff (like we are doing for security updates now).
That's a start.
> I would to raise another point here quickly, but it needs its own thread:
> shouldn't we force release specific rpms? Too many people are using cooker
> rpms on stable version. Too many people are using rpms for different
> versions on their stable version.
I've already suggested something like this in a previous thread. I
thought about a distribution epoch for all packages, so that official
packages are always newer than backported packages. This would need
some rpm changes, so that a package built on 9.2 would have an epoch
of 92 and one build on 10.0 would have epoch 100. But this would be a
problem with packages that already has an epoch, as you can use only
integer numbers for the epoch tag.
The problem of your naming is that you have to change it by hand. I'd
like to rebuild a cooker package on a stable distribution version and
have it's release changed automatically.
CU
--
What difference does it make to the dead, the orphans and the
homeless, whether the mad destruction is wrought under the name of
totalitarianism or the holy name of liberty or democracy?
Mahatma Gandhi (1869 - 1948), "Non-Violence in Peace and War"