From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OpenEmbedded Development mailing list
<openembedded-devel@lists.openembedded.org>
Subject: what's the purpose of tarballs in the OE repo?
Date: Sat, 16 Jan 2010 14:42:45 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.1001161439340.13406@localhost> (raw)
following up on a thread from the bitbake dev ML, what is the
purpose of actual tarballs in the OE dev repository?
$ find . -name *tar.gz
./recipes/firmwares/marvell-gspi-fw/9.70.3-p37.tar.gz
./recipes/firmwares/marvell-sdio-fw/9.70.3-p37.tar.gz
./recipes/x-load/files/x-loader-03.00.00.01.tar.gz
./recipes/sgalib/sgalib-0.1.0/sgalib-0.1.0.tar.gz
./recipes/qpealarmclock/qpealarmclockapplet-1.0.9/missing-files.tar.gz
./recipes/zaurus-utils/files/gnu-tar.gz
$
$ find . -name *tar.bz2
./recipes/powervr-drivers/omap3-sgx-modules/omap3-sgx-modules-1.3.13.1607.tar.bz2
./recipes/supertux/files/supertux-smallsize-data.tar.bz2
$
i assume they're there because they're not available for
unrestricted download from somewhere on the net, but is that the case
for all of them? shouldn't some of them be moved into a net repo
somewhere?
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================
next reply other threads:[~2010-01-16 19:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-16 19:42 Robert P. J. Day [this message]
2010-01-17 0:24 ` what's the purpose of tarballs in the OE repo? Rolf Leggewie
2010-01-17 7:55 ` Robert P. J. Day
2010-01-17 10:46 ` Holger Hans Peter Freyther
2010-01-17 14:52 ` Robert P. J. Day
2010-01-17 9:45 ` Odp.: " Marcin Juszkiewicz
2010-01-17 12:46 ` [OT] What does »Odp.« stand for? (was: Odp.: what's the purpose of tarballs in the OE repo?) Paul Menzel
2010-01-17 12:51 ` Phil Blundell
2010-01-17 21:33 ` Marcin Juszkiewicz
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=alpine.LFD.2.00.1001161439340.13406@localhost \
--to=rpjday@crashcourse.ca \
--cc=openembedded-devel@lists.openembedded.org \
/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.