All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/3] package/cal3d: new package
Date: Sat, 19 Dec 2015 15:35:19 +0100	[thread overview]
Message-ID: <20151219153519.38c52050@free-electrons.com> (raw)
In-Reply-To: <20151219142509.GA3394@free.fr>

Yann,

On Sat, 19 Dec 2015 15:25:09 +0100, Yann E. MORIN wrote:

> But in this precise case, I would:
>   - dump the cal3d package
>   - add a post-download hook (or an extra-download URL) to vsxu to also
>     download cal3d

A post-download hook wouldn't play well with "make source", "make
legal-info" and all. We have to take this into account. But an
EXTRA_DOWNLOADS should work fine.

>   - add a post-extract hook to vsxu to also extract cal3d in the correct
>     location.

Could be a solution, I'll try this.

> Otherwise, for proper git-submodule handling, we would have to do
> (roughly):
> 
>     git clone blabla pkg-version
>     cd pkg-version
>     git checkout pkg-version
>     git submodule update --init --recursive
>     find . -name .git -exec rm -rf {} +
>     cd ..
>     tar czf DL_DIR/pkg-version.tar.gz pkg-version/
> 
> This is not very complex, but is stil la significant change from our
> current git wrapper.
> 
> And then, what about svn externals? About Hg subrepos? Does bzr also
> have such a thing?
> 
> Note that I would not really mind doing such a change. But is it worth
> it, given that we currently have only one package that needs submodules?
> Or do we have others for which we had to "deal with it" in a crude way?

I don't want to go down this route for the moment, I'd prefer to see
how many of these git submodule users we have.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2015-12-19 14:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-07 16:50 [Buildroot] [PATCH v2 0/3] New packages libglfw/cal3d/vsxu Bernd Kuhls
2015-11-07 16:50 ` [Buildroot] [PATCH v2 1/3] package/libglfw: new package Bernd Kuhls
2015-12-19 13:59   ` Thomas Petazzoni
2015-11-07 16:50 ` [Buildroot] [PATCH v2 2/3] package/cal3d: " Bernd Kuhls
2015-12-19 14:00   ` Thomas Petazzoni
2015-12-19 14:25     ` Yann E. MORIN
2015-12-19 14:35       ` Thomas Petazzoni [this message]
2015-12-19 14:47       ` Arnout Vandecappelle
2015-12-20 21:52       ` Peter Korsgaard
2015-12-19 14:35     ` Arnout Vandecappelle
2015-12-19 14:39   ` Arnout Vandecappelle
2015-11-07 16:50 ` [Buildroot] [PATCH v2 3/3] package/vsxu: " Bernd Kuhls
2015-12-19 14:43   ` Arnout Vandecappelle
2015-12-19 15:14   ` Thomas Petazzoni

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=20151219153519.38c52050@free-electrons.com \
    --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 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.