From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Source download overwrite
Date: Fri, 14 Nov 2014 14:14:45 +0100 [thread overview]
Message-ID: <20141114141445.77f68c2d@free-electrons.com> (raw)
In-Reply-To: <CAOFH_kEf-xur6tPGZb8rhA=211gK=Ww4tS0HRVpOe6KA-WEQMw@mail.gmail.com>
Dear Mathieu Slabbinck,
On Fri, 14 Nov 2014 10:24:58 +0100, Mathieu Slabbinck wrote:
> Hi,
>
> I'm looking for a way to overwrite the internal download system of buidroot
> for a specific homebrew package.
>
> The goal of the package is to download multiple files and install them
> accordingly.
> LIBFOO_SITE contains the common part of the download link. For example
> ftp://myftpserver.mydomain.com/libfoo/.
>
> Then I'd like to have a pre-install hook that downloads some specific files
> from that url, for example
> - ftp://myftpserver.mydomain.com/libfoo/file1.deb
> - ftp://myftpserver.mydomain.com/libfoo/file2.rpm
> - ftp://myftpserver.mydomain.com/libfoo/file3.someExtension
>
> This all works fine, but the package still tries to fetch
> ftp://myftpserver.mydomain.com/libfoo/.tar.gz because of the internal way
> of working of buildroot.
>
> So how can I overwrite this method or disable it?
Why don't you simply use the <pkg>_EXTRA_DOWNLOADS variable? It allows
you to download additional files from the same site, which seems to be
exactly what you're trying to achieve.
LIBFOO_SITE = ftp://myftpserver.mydomain.com/libfoo/
LIBFOO_SOURCE = <one file>
LIBFOO_EXTRA_DOWNLOADS = <another file> <yet another file>
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-11-14 13:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-14 9:24 [Buildroot] Source download overwrite Mathieu Slabbinck
2014-11-14 13:14 ` Thomas Petazzoni [this message]
2014-11-14 14:27 ` Mathieu Slabbinck
2014-11-14 14:33 ` Thomas Petazzoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141114141445.77f68c2d@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox