Bug#762175: gnumach: Introduce kernel versions?
Svante Signell, le Fri 19 Sep 2014 10:19:06 +0200, a écrit :
> With the attached path to debian/rules, these names become unique,
> enabling installation of multiple versions as is the case for
> GNU/Linux:
> gnumach-1.4-12-486.gz
> etc.
>
> Unless problems arise with reject from Debian's NEW-Queue when new
> versions are uploaded,
They won't be rejected, but it will be a huge pain to have to see
gnumach go through the NEW queue for each and every gnumach upload. That
will really not fly. Linux only uses versions for its module ABI, which
doesn't change often. We don't have such kind of thing, so we have no
reason to introduce these versions in the archive and get the pain.
We can however let the user do it for his own purpose.
> If not accepted, maybe the patch can be modified to use the new naming
> scheme conditionally, so that custom built images can be installed in
> parallel to the stock versions:
>
> export CUSTOM_KERNEL=yes
>
> debian/rules:
> ifeq ($(CUSTOM_KERNEL),yes)
> DEB_VERSION := $(VERSION)
> endif
Yes, that will fly.
However, the patch is missing something (did you completely try it
actually?): it has to modify debian/control, otherwise the package names
will be kept the same, and the user won't be able to co-install them
along the archive ones. It thus mean auto-generating debian/control,
probably something like the linux or the glibc packages do.
Samuel
Reply to: