[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: kernel-package tar file unpacks into ./linux/

>>"Ian" == Ian Jackson <ian@chiark.chu.cam.ac.uk> writes:

Ian> srivasta@pilgrim.umass.edu writes ("kernel-package tar file
Ian> unpacks into ./linux/"):

>> :: Manoj, Could you seriously consider making the tar.gz file
>> upload :: in the current directory, not in ./linux? It's painful to
>> have to :: move a linux link to point to my various kernel sources
>> (I do :: have some...) just to unpack your really nice package.

>> Would this be a major problem for people who use kernel-package?
>> (this may not be a big disaster anyway, since even if the user
>> expects the tar file to unpack in ./linux and it unpacks into
>> ./ , one just removes debian* in the current directory. IMHO it is
>> unlikely to stopm over any files, since one would not normally
>> unpack it in a directory with debian* files).

Ian> I'm afraid I don't like this change at all.  One of the best
Ian> things about the GNU world and Debian too is that you can unpack
Ian> almost any tarfile without having it splatter stuff all over your
Ian> current directory, making a mess that can be very hard to clean
Ian> up.

Ian> I think that the kernel-package you supply should do the same
Ian> thing as Linus's kernels.

Ian> I think that Linus's kernels should unpack into linux-<version>
Ian> rather than linux, but that's up to him and you should follow his
Ian> lead.

Ian> If you don't like the linux level you can use a symlink or say mv
Ian> linux/* .

	I'm afraid that this was indeed my personal preference (which
is why the original behaviour was to unpack into ./linux).  However, I
have recieved four enthusiastic notes for it, and this is the forst
strong one against the motion.

	I think that we have to evaluate the ease of use for people
who know about the package, and unpack kernel sources elsewhere than
in ./linux; and the infelicity of having the tar file leave droppings
all over the current directory in case one unpacks it in the wrong
directory (not having read the documentation, nor having investigated
the archive).

	A point to note is that this is a package in the *experimental*
section, and is not targeted towards the casual user. Also, all the
files contained have the prefix debian, so it is not that onerous a
task cleaning the files up even when one makes this error.

	I this this issue is a matter of aesthetics, and I have no
strong views on it, but I _am_ resistant to changing it back for no
other reason than aesthetics (if for nothing else than for the
confusion such flip-flopping is sure to cause). I'm open to being
convinced, though, espescially if some kind of consensus is achieved
(and of course to a fiat ;-).


How many NASA managers does it take to screw in a lightbulb?  "That's
a known problem... don't worry about it."  
Manoj Srivastava               Systems Research Programmer, Project Pilgrim,
Phone: (413) 545-3918                A143B Lederle Graduate Research Center,
Fax:   (413) 545-1249         University of Massachusetts, Amherst, MA 01003
<srivasta@pilgrim.umass.edu> <URL:http://www.pilgrim.umass.edu/%7Esrivasta/>

Reply to: