From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] toolchain package: set version as 'virtual' instead of 'undefined'
Date: Thu, 08 May 2014 08:59:01 +0200 [thread overview]
Message-ID: <536B2B35.90906@mind.be> (raw)
In-Reply-To: <CAAXf6LUsgmETOjUQhCZ1fPAhXOyneYFpuu8G=XKX0W9yx4nuKg@mail.gmail.com>
On 06/05/14 14:46, Thomas De Schampheleire wrote:
> On Tue, May 6, 2014 at 2:38 PM, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
>> Dear Thomas De Schampheleire,
>>
>> On Tue, 6 May 2014 14:26:31 +0200, Thomas De Schampheleire wrote:
>>
>>>> Shouldn't we instead migrate these to use the virtual package
>>>> infrastructure, and make this infrastructure define this magic 'virtual'
>>>> version?
>>>
>>> For toolchain and toolchain-buildroot that would be possible, but for
>>> toolchain-external not, right?
>>
>> Right. But toolchain-external is not a virtual package, so setting its
>> version to 'virtual' would anyway be strange, no?
>
> Not more strange than setting the version to 'undefined' :-D
>
> Any other string than 'undefined' is fine for me too.
>
> Btw, for makedevs and mkpasswd, the version is also 'undefined' as the
> source is included in buildroot.
> I was first going to change their version to 'buildroot', but it makes
> the messages a bit strange:
>
>>>> host-makedevs buildroot Configuring...
MAKEDEVS_VERSION = buildroot-$(BR2_VERSION)
?
Regards,
Arnout
--
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: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2014-05-08 6:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 10:51 [Buildroot] [PATCH] toolchain package: set version as 'virtual' instead of 'undefined' Thomas De Schampheleire
2014-05-06 12:07 ` Thomas Petazzoni
2014-05-06 12:26 ` Thomas De Schampheleire
2014-05-06 12:38 ` Thomas Petazzoni
2014-05-06 12:46 ` Thomas De Schampheleire
2014-05-08 6:59 ` Arnout Vandecappelle [this message]
2014-05-06 20:05 ` Thomas De Schampheleire
2014-05-07 19:26 ` Thomas De Schampheleire
2014-05-07 19:37 ` Thomas De Schampheleire
2014-05-08 7:04 ` Thomas De Schampheleire
2014-05-08 8:31 ` Arnout Vandecappelle
2014-05-08 9:28 ` Thomas De Schampheleire
2014-05-08 9:52 ` Arnout Vandecappelle
2014-05-08 11:37 ` Thomas De Schampheleire
2014-05-08 13:00 ` Arnout Vandecappelle
2014-05-08 20:03 ` Thomas De Schampheleire
2014-05-08 22:18 ` Arnout Vandecappelle
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=536B2B35.90906@mind.be \
--to=arnout@mind.be \
--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