From: Alex Suykov <alex.suykov@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC 1/2] non-versioned packages
Date: Thu, 1 Oct 2015 01:52:34 +0300 [thread overview]
Message-ID: <20150930225234.GA29781@vostro> (raw)
In-Reply-To: <20150930221517.GA3702@free.fr>
Thu, Oct 01, 2015 at 12:15:17AM +0200, Yann E. MORIN wrote:
> And yes, I would like to keep being able to have packages without a
> version.Even if upstream are not playing by the rules, it is perfectly
> legit that we have support for that.
Sorry, bad wording in patch description. Packages with explicitly
set (PKG)_SOURCE are ok, they only get build dir name change:
output/build/initscripts-undefined -> output/build/initscripts and so on.
The change is for packages that lack both _VERSION and _SOURCE.
Current BR behavior is to assign (PKG)_SOURCE = (pkg)-undefined.tar.gz
and try to download that, which I think is never correct.
It's either explicitly-set custom SOURCE, or no sources at all.
next prev parent reply other threads:[~2015-09-30 22:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-30 21:12 [Buildroot] [RFC 1/2] non-versioned packages Alex Suykov
2015-09-30 21:13 ` [Buildroot] [RFC 2/2] remove download suppression from mke2img and skeleton Alex Suykov
2016-01-19 22:33 ` Yann E. MORIN
2016-01-20 14:14 ` Thomas De Schampheleire
2016-01-25 0:16 ` Arnout Vandecappelle
2015-09-30 22:15 ` [Buildroot] [RFC 1/2] non-versioned packages Yann E. MORIN
2015-09-30 22:52 ` Alex Suykov [this message]
2015-10-15 20:41 ` Thomas Petazzoni
2015-10-15 22:31 ` Arnout Vandecappelle
2016-01-19 22:32 ` Yann E. MORIN
2016-01-24 22:33 ` Alex Suykov
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=20150930225234.GA29781@vostro \
--to=alex.suykov@gmail.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