Tushar Teredesai wrote:
On 12/31/05, Dan McGhee <[EMAIL PROTECTED]> wrote:
Of course, I would be doing this in addition to the things suggested in
the hint on smaller systems. I'm just looking for, "Sounds like it will
work," or "Don't do it numbskull!"
It will work if you are careful :) But I don't know how practical it
would be. For the example that you mentioned, cpio is only a
build-time dependency for JDK, so you can remove it after installing
the JDK. But if you ever want to upgrade JDK, you will need to
reinstall cpio. So unless you plan to rebuild the entire system for
every package upgrade, removing build time dependencies is not very
useful.
Thanks, Tushar. Both you and Randy talked about the bother and the time
it would take to do this. Since, I'm such a lazy, cheapskate [:-)]
space on my laptop hard drive is precious. After reading the responses
to this post, I have decided that I will remove only those items that
don't install libraries. As far as things like cpio, and other
applications that are required for things only at build time, I don't
mind rebuilding them each time I install a package that needs them.
Just had an idea as I was responding to you. ( I know. That's scary.)
Since I make a list of all files a package installs, I could " tar 'em
up" and then remove them. That way I wouldn't have to rebuild, just
untar. I could keep the tar files on a disk instead of the hard drive.
Thanks for your response.
Dan
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
