From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC PATCH 0/2] gitorious helper
Date: Fri, 10 Jan 2014 16:35:10 +0800 [thread overview]
Message-ID: <20140110163510.1d2c8d8a@skate> (raw)
In-Reply-To: <CAAXf6LWy3cXCxTLZcPo+pgXeHjNwc2+uVGyJZZLYJ8RP2rCFHA@mail.gmail.com>
Dear Thomas De Schampheleire,
On Wed, 8 Jan 2014 08:54:37 +0100, Thomas De Schampheleire wrote:
> 1. discuss the situation with the Gitorious people, requesting them to
> provide a downloadable tarball with the name
> <package>-<version>.tar.gz (or whichever extension), like the rest of
> the software world does.
This would be an interesting thing to do, indeed.
> 2. accept the fact that the URL cannot be changed, but modify the wget
> download helper so that it can rename the file after download
> (clarifying the list of files in dl/)
>
> In the first alternative, the gitorious helper can be a one-liner just
> as for github, and the .mk files only need to specify FOO_SITE.
> In the second alternative, we need to set two variables FOO_SITE and
> FOO_SOURCE. In your current patchset, you have done this with one
> helper that sets both variables. As a result, the usage compared to
> the github helper is fundamentally different.
> For github:
> FOO_SITE = $(call github,username,package,$(FOO_VERSION))
> while for gitorious:
> $(call gitorious,username,package,$(FOO_VERSION)
>
> I don't like this difference, and suggest two alternatives:
> A. split the helper in two, so that:
> FOO_SITE = $(call gitorious-site,username,package,$(FOO_VERSION))
> FOO_SOURCE = $(call gitorious-version,username,package,$(FOO_VERSION))
I very much prefer this solution. I don't really like the helper that
magically defines FOO_SITE and FOO_VERSION.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-01-10 8:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-25 16:18 [Buildroot] [RFC PATCH 0/2] gitorious helper Alexandre Belloni
2013-12-25 16:18 ` [Buildroot] [PATCH 1/2] infra: introduce gitorious helper function Alexandre Belloni
2013-12-25 16:18 ` [Buildroot] [PATCH 2/2] packages: use gitorious helper when applicable Alexandre Belloni
2014-01-04 16:20 ` [Buildroot] [RFC PATCH 0/2] gitorious helper Thomas De Schampheleire
2014-01-08 7:54 ` Thomas De Schampheleire
2014-01-10 8:35 ` Thomas Petazzoni [this message]
2014-04-29 5:11 ` Alexandre Belloni
2014-04-29 5:18 ` Thomas De Schampheleire
2014-04-29 5:28 ` Alexandre Belloni
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=20140110163510.1d2c8d8a@skate \
--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