Jeff:
Sorry you don't agree. What I mean to say was, suppose
my currently running system has a working /etc/dnscache (for
example). I'd be ill advised to extract a new dnscache.lrp without
carefully controlling where it untar's. The defaults would overwrite
what's my system was using.
Also, I don't see untar'ing to /tmp a lot of extra work.
As I recall, lrcfg backs up to /tmp before writing to a floppy, and
I've never heard it so characterized. But, to each their own.
-Scott
>> Actually I like .lrp as well, though my complaint
>> with it is different. I find it difficult to extract files
>> from a .lrp without potentially overwriting important system
>> binaries on the development box.
>
>I don't grok this. I have never had difficulty extracting or creating lrp
>files in the subdirectory of my choice. System files are in no danger.
>
>> What'd be *much* nicer is if package.lrp expanded
>> to /tmp/package, and then /tmp/package/package.list would be
>> queried to find out where to put everything.
>
>I don't agree. What a lot of extra work.
_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel
