From: "Andreas Färber" <afaerber@suse.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [ANN] git server, FTP server
Date: Sun, 19 Jul 2015 18:59:56 +0200 [thread overview]
Message-ID: <55ABD78C.2060108@suse.de> (raw)
In-Reply-To: <20150715125134.E32AF381009@gemini.denx.de>
Dear Wolfgang,
Am 15.07.2015 um 14:51 schrieb Wolfgang Denk:
> In message <593AEF6C47F46446852B067021A273D6FBC788CC@MUCSE037.lantiq.com> you wrote:
>>
>> I tried to find a way to download a file with wget or a similar tool, which
>> would be used by a distribution builder (like Yocto, Buildroot, OpenWrt, ...).
>
> Why would any build environment use tarballs? can you not just
> reference the git repository? This is much more efficient, IMHO.
Open Build Service uses tarballs, too. We usually specify full URLs in
the RPM .spec file [1] both for documentation of origin and so that the
mirrored tarball can be verified via gpg or checksum where available.
As the actual build is intentionally done offline, at some point a
tarball is needed. The URL could happily be a redirect to some mirror.
When developing, Git is great of course.
Regards,
Andreas
[1]
https://build.opensuse.org/package/view_file/Base:System/u-boot/u-boot.spec.in?expand=1
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
GF: Felix Imend?rffer, Jane Smithard, Dilip Upmanyu, Graham Norton; HRB
21284 (AG N?rnberg)
next prev parent reply other threads:[~2015-07-19 16:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 7:24 [U-Boot] [ANN] git server, FTP server Wolfgang Denk
2015-07-15 8:34 ` Igor Grinberg
2015-07-15 8:51 ` Bin Meng
2015-07-15 12:35 ` Wolfgang Denk
2015-07-15 13:16 ` Bin Meng
2015-07-17 5:29 ` Wolfgang Denk
2015-07-15 9:03 ` Andy Pont
2015-07-15 9:32 ` thomas.langer at lantiq.com
2015-07-15 12:51 ` Wolfgang Denk
2015-07-19 16:59 ` Andreas Färber [this message]
2015-07-19 21:48 ` Peter Robinson
2015-07-20 19:33 ` Wolfgang Denk
2015-07-20 19:30 ` Wolfgang Denk
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=55ABD78C.2060108@suse.de \
--to=afaerber@suse.de \
--cc=u-boot@lists.denx.de \
/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