From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/7 v4] support/test-pkg: fixes and enhancements
Date: Thu, 6 Apr 2017 17:55:54 +0200 [thread overview]
Message-ID: <20170406155554.GB3538@scaer> (raw)
In-Reply-To: <573ed965-5286-80a8-b4b6-291998013137@mind.be>
Arnout, All,
On 2017-04-06 10:48 +0200, Arnout Vandecappelle spake thusly:
> On 05-04-17 21:16, Yann E. MORIN wrote:
> > On 2017-04-05 16:37 +0200, Arnout Vandecappelle spake thusly:
> >> I was going to modify test-pkg to use the toolchains from configs/toolchains,
> >> but then I noticed this series was still not committed. It obviously conflicts
> >> heavily with what I'm going to do, so I'm taking this over, OK?
> > The latest version (which I did not yet post, did I?) is available, as
> > usual, on my git tree:
> > git://git.busybox.net/~ymorin/git/buildroot yem/test-pkg
> Argh, I should have checked for that before starting my work... Your commits
> don't have a version log, do you have any idea if anything changed except for
> the first patch?
Given that the first patch does have a changelog, but the others do not,
I guess nothing of great interest... :-/
> > Well, as long as I can specify a list of toolchains, that is not the
> > default, that's fine. If I just have to do a wget to have a local file,
> > I'm OK with that.
> >
> > But I *want* to be able to use a custom list of toolchains.
>
> You don't need to get it from a URL, do you? I think having the list of
> toolchains passed as a BR2_EXTERNAL is much more appropriate. Basically, I now have
>
> TOOLCHAINS_PATH=configs/toolchains
Please, make that an option to the script, not an environment variable!
--toolchains-dir=/path/to/configs/toolchains
> which points to a directory containing toolchain configs. I can add an option
> that allows you to override that directory. I don't see much point in getting
> this from a URL, is there?
Well, if I can use a custom list of toolchians, I'm fine. Now, that I
need to pre-populate that directory by myself is acceptable. If I need
to store the toolchain configs remotely, it now behooves to me to
download them fiurst and feed local files to the script. That's OK.
> >>> support/test-pkg: print number of toolchain and progress
> >>> support/test-pkg: the list of toolchains really contains URLs
> >> With the toolchain URLs gone, this is not true anymore.
> > Well, I am not sure what you meant: we can't have a list of remote
> > config files to use anymore? That is sad... :-(
> Can you explain your use case for a list of *remote* config files?
It's just that my "tool_s_" are stored in their own repositor_ies_...
Regards,
Yann E. MORIN.
> > Please note that there is another patch on the series now:
> > support/test-pkg: run legal-info
> It was already there (see below).
/me rubs his eyes...
Ah, right...
Regards,
Yann E. MORIN.
> Regards,
> Arnout
>
> >
> > https://git.buildroot.org/~ymorin/git/buildroot/commit/?h=yem/test-pkg&id=8a9fec1b939caad8ad282a94e6049c748eff5336
> >
> > Regards,
> > Yann E. MORIN.
> >
> >>
> >> Regards,
> >> Arnout
> >>
> >>> support/test-pkg: run legal-info
> >>>
> >>> docs/manual/adding-packages-tips.txt | 91 +++++++++++++++++++++++++++++++
> >>> support/scripts/test-pkg | 101 +++++++++++++++++++++++------------
> >>> 2 files changed, 159 insertions(+), 33 deletions(-)
> >>>
> >>
> >> --
> >> Arnout Vandecappelle arnout at mind be
> >> Senior Embedded Software Architect +32-16-286500
> >> Essensium/Mind http://www.mind.be
> >> G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
> >> LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
> >> GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
> >
>
> --
> Arnout Vandecappelle arnout at mind be
> Senior Embedded Software Architect +32-16-286500
> Essensium/Mind http://www.mind.be
> G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
> LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
> GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2017-04-06 15:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 21:44 [Buildroot] [PATCH 0/7 v4] support/test-pkg: fixes and enhancements Yann E. MORIN
2017-02-15 21:44 ` [Buildroot] [PATCH 1/7 v4] docs/manual: document the test-pkg script Yann E. MORIN
2017-02-15 22:25 ` Thomas Petazzoni
2017-02-16 17:21 ` Yann E. MORIN
2017-02-15 21:44 ` [Buildroot] [PATCH 2/7 v4] support/test-pkg: add option to use an alternate list of toolchains Yann E. MORIN
2017-02-15 21:44 ` [Buildroot] [PATCH 3/7 v4] support/test-pkg: print number of toolchain and progress Yann E. MORIN
2017-02-15 21:44 ` [Buildroot] [PATCH 4/7 v4] support/test-pkg: the list of toolchains really contains URLs Yann E. MORIN
2017-02-15 21:44 ` [Buildroot] [PATCH 5/7 v4] support/test-pkg: cannonicalize paths early Yann E. MORIN
2017-02-15 21:44 ` [Buildroot] [PATCH 6/7 v4] support/test-pkg: create build dir from caller Yann E. MORIN
2017-02-15 21:44 ` [Buildroot] [PATCH 7/7 v4] support/test-pkg: run legal-info Yann E. MORIN
2017-04-05 14:37 ` [Buildroot] [PATCH 0/7 v4] support/test-pkg: fixes and enhancements Arnout Vandecappelle
2017-04-05 19:16 ` Yann E. MORIN
2017-04-06 8:48 ` Arnout Vandecappelle
2017-04-06 15:55 ` Yann E. MORIN [this message]
2017-04-06 17:19 ` Arnout Vandecappelle
-- strict thread matches above, loose matches on Subject: below --
2017-02-12 14:53 Yann E. MORIN
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=20170406155554.GB3538@scaer \
--to=yann.morin.1998@free.fr \
--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