From: George Shapovalov <george@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] Hello
Date: Tue, 12 Oct 2004 13:37:20 -0700 [thread overview]
Message-ID: <200410121337.20556.george@gentoo.org> (raw)
In-Reply-To: <416C3857.9030109@sendmail.com>
On Tuesday 12 October 2004 13:02, Ashish Gawarikar wrote:
> I am trying to have a one-meta-package, that contain the other
> packages, but I would not be exposing the other
> packages on my download site. For example:
>
> foo-1.0.0.ebuild will not be available to be downloaded from the
> download site, and even bar-1.0.0.ebuild.
> They will be only available in the dummy-1.0.0.ebuild.
[skip]
> My goal is to download one-meta-package, that has other packages
> self-contained. On the rpm side of the world
> "rpm of rpms", so that I dont have to mantain the other packages on my
> download site, and one package download
> will contain all the dependent packages within.
Hm, I am afraid there is no trivial way to do this, short of collating
contents of all these packages in a single ebuild. However this:
1. is ugly
2. will not work if there are interdependencies within this set of packages
Well, it should be possible if you split this package in two (and if it is
only the downloading part that you want to combine):
one downloads and unpacks the meta-tarball that you package yourself (should
have src_unpack placing extracted individual tarballs into ${D}/${DISTDIR}
and empty scr_compile/install)
second just lists the dependencies as mentioned before.
Although I fail to see why would you want to do something like that. I mean
what is the situation when it is better to roll your own meta tarballs rather
than fetch individual ones? Well, bittorrent will be more efficient with
single large package rather than multiple small ones, but other than that I
am quite puzzled :).
George
--
gentoo-portage-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-10-12 20:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-12 18:56 [gentoo-portage-dev] Hello Ashish Gawarikar
2004-10-12 19:10 ` George Shapovalov
2004-10-12 20:02 ` Ashish Gawarikar
2004-10-12 20:37 ` George Shapovalov [this message]
2004-10-12 21:00 ` ashish gawarikar
2004-10-12 21:26 ` Nick Dimiduk
2004-10-12 21:36 ` Colin Kingsley
2004-10-13 0:46 ` George Shapovalov
2004-10-13 0:58 ` George Shapovalov
2004-10-12 23:09 ` George Prowse
2004-10-13 7:57 ` Paul de Vrieze
2004-10-12 20:06 ` Paul de Vrieze
2004-10-12 20:40 ` Marius Mauch
2004-10-13 9:43 ` Sven Vermeulen
2004-10-13 10:04 ` Paul de Vrieze
2004-10-13 12:22 ` Marius Mauch
-- strict thread matches above, loose matches on Subject: below --
2011-05-31 20:38 [gentoo-portage-dev] hello ferringb
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=200410121337.20556.george@gentoo.org \
--to=george@gentoo.org \
--cc=gentoo-portage-dev@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox