From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/4] core/pkg-infra: introduce download features concept
Date: Fri, 17 Jan 2020 09:17:55 +0100 [thread overview]
Message-ID: <20200117091755.69711c60@windsurf> (raw)
In-Reply-To: <b782018a-bec1-07d5-da24-128d4eba2a1b@mind.be>
On Thu, 16 Jan 2020 23:59:00 +0100
Arnout Vandecappelle <arnout@mind.be> wrote:
> It's good to fire it off early (as an RFC) to avoid wasting work if it's going
> in the wrong direction.
>
> ... which I think this is.
>
> I guess the idea is to generalize the submodules feature so it can be used by
> several VCS systems, and to combine it with the transient option.
>
> However, I don't think the additional complexity is worth it.
>
> Separate _GIT_SUBMODULES = YES and _DOWNLOAD_TRANSIENT = YES are IMO easier to
> understand than _DL_FEATURES = submodules transient, because we don't really
> have the latter pattern anywhere else in Buildroot. In addition, it's hard to
> remember if it's comma-separated or space-separated.
I asked the exact same question on IRC before Vincent sent his patch
series, and both Yann and me suggested that it should be sent with
actual examples of how the DL_FEATURES mechanism will be used.
The intention of Vincent is not to use this DL_FEATURES variable for
"transient", but rather to implement download method specific things,
and the first example was git-lfs support.
transient would remain a separate variable. transient is independent of
the download method: it only tells the download infrastructure to
ignore the cache, and always redownlaod from upstream, regardless of
the download method.
DL_FEATURES however would be to pass backend-specific flags.
That being said, I agree that with just two flags for the moment
(submodules and git-lfs), it's not clear this is really needed. Also,
this DL_FEATURES mechanism only allows to pass booleans, which works
fine for submodules and git-lfs, but what if we want to pass some
actual value to a download backend (like a timeout value, or some other
thing).
So maybe with just two booleans for now, we should stick to
<pkg>_GIT_SUBMODULES = YES and <pkg>_GIT_LFS = YES ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-01-17 8:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 19:38 [Buildroot] [PATCH 1/4] core/pkg-infra: introduce download features concept Vincent Fazio
2020-01-16 19:38 ` [Buildroot] [PATCH 2/4] support/download/git: support download features Vincent Fazio
2020-01-16 19:38 ` [Buildroot] [PATCH 3/4] core/pkg-infra: deprecate GIT_SUBMODULES Vincent Fazio
2020-01-16 19:38 ` [Buildroot] [PATCH 4/4] package/*: migrate GIT_SUBMODULES to DL_FEATURES Vincent Fazio
2020-01-16 19:49 ` [Buildroot] [PATCH 1/4] core/pkg-infra: introduce download features concept Ryan Barnett
2020-01-16 19:53 ` Vincent Fazio
2020-01-16 22:59 ` Arnout Vandecappelle
2020-01-17 8:17 ` Thomas Petazzoni [this message]
2020-01-17 13:56 ` Vincent Fazio
2020-01-17 16:44 ` Yann E. MORIN
2020-01-20 8:56 ` Arnout Vandecappelle
2020-01-20 20:38 ` Vincent Fazio
2020-01-20 21:07 ` Arnout Vandecappelle
2020-01-20 21:26 ` Vincent Fazio
2020-01-21 22:21 ` Arnout Vandecappelle
2020-01-22 13:56 ` Vincent Fazio
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=20200117091755.69711c60@windsurf \
--to=thomas.petazzoni@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.