On 9/25/06, M.Canales.es <[EMAIL PROTECTED]> wrote:

For jhalfs, first we must to make mandatory the linux kernel package download
(at this moment the kernel  download/build is optional to allow folks to
upgrade their kernel sources using patches). Then we will need to map the new
headers page script name to the kernel package name, to can unpack it. Maybe
some other fix could be needed, but we can't know until see the commands on
that new page.

(More appropriate for alfs-discuss)

I've been thinking about this for a while. Is there any reason why
jhalfs doesn't use the $package-url entity to find out the tarball
instead of assuming that there is a 1:1 mapping between package and
tarball? With a small shell function (or xsl if it's easier), you
could strip out the tarball name and figure out the directory
(approximately using tar -tf $tarball | head -n1). Then you could get
rid of the ugliness in get_package_tarball_name() and get_sources().
If you think it could be done, I'd be glad to work on it. I think this
could also be done as a make function.

--
Dan
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Reply via email to