From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Jose Quaresma <quaresma.jose@gmail.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] gstreamer: use git to fetch the sources
Date: Sat, 31 Oct 2020 00:32:08 +0000 [thread overview]
Message-ID: <aa090613e34863ee936811011d3019eafba3db81.camel@linuxfoundation.org> (raw)
In-Reply-To: <20201030232256.624297-1-quaresma.jose@gmail.com>
On Fri, 2020-10-30 at 23:22 +0000, Jose Quaresma wrote:
> gstreamer has the code hosted on [1] and this repo as tags.
> manage code with git its more convenient than with tarball archives.
>
> [1] - https://gitlab.freedesktop.org/gstreamer
>
> Signed-off-by: Jose Quaresma <quaresma.jose@gmail.com>
I'm not 100% sure about this. Tarballs tend to be less overhead for
fetching and make for easier source archiving. The git repos are easier
for day to day dev work but tend to be harder for the AUH to handle and
slower to fetch for the users taking up more space to download and
unpack. I'm therefore torn. I know where we have used git for other
core components it has caused performance issues.
We do also have the option of the devupstream class although I know
that doesn't quite work for the native cases yet sadly.
Cheers,
Richard
next prev parent reply other threads:[~2020-10-31 0:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 23:22 [PATCH] gstreamer: use git to fetch the sources Jose Quaresma
2020-10-31 0:32 ` Richard Purdie [this message]
2020-10-31 11:40 ` [OE-core] " Jose Quaresma
2020-10-31 12:29 ` Andrey Zhizhikin
2020-10-31 13:15 ` Martin Jansa
2020-10-31 16:54 ` Andrey Zhizhikin
2020-10-31 20:29 ` Otavio Salvador
2020-11-01 21:16 ` Jose Quaresma
[not found] ` <16437EE3A0B6A44A.10137@lists.openembedded.org>
2020-11-05 9:32 ` Jose Quaresma
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=aa090613e34863ee936811011d3019eafba3db81.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=quaresma.jose@gmail.com \
/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.