Re: backwards compatibility was Re: Uploaded kernel-package 3.61
Hi,
>>"Kai" == Kai Henningsen <kaih@khms.westfalen.de> writes:
Kai> srivasta@datasync.com (Manoj Srivastava) wrote on 19.02.98 in
Kai> <[🔎] 87wwer2njv.fsf@tiamat.datasync.com>:
>> Firstly, this is not just a hamm issue. Suppose I remove the files,
>> and people upload 2.0.34 with the new kernel-package.
>>
>> Hamm is then released, people upgrade, and use the new kernel (no
>> more /usr/src/.linux-version or lunix* links). Then they try to get
>> rid og old kernel images, and all hell breaks loose.
Kai> Umm - why would there be a problem? What, exactly, would break?
Sorry, I was typing half asleep, I think. I meant old kernel
headers or kernel sources packages shall break, and return exit
status 1 to dpkg.
How bad that is is left to you. Looking at chapter 6 of the
packaging manual, this may not be as bad as I thought.
So, if people ask nicely , I may consider removing the
symlinks before the freeze.
manoj
who is really distressed by having flip-flopped so many times on this
issue.
--
There was a young peasant named Gorse Who fell madly in love with his
horse. Said his wife, "You rapscallion, That horse is a stallion--
This constitutes grounds for divorce."
Manoj Srivastava <srivasta@acm.org> <http://www.datasync.com/%7Esrivasta/>
Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org .
Trouble? e-mail to templin@bucknell.edu .
Reply to: