From: Ashish Gawarikar <ashish@sendmail.com>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] Hello
Date: Tue, 12 Oct 2004 13:02:31 -0700 [thread overview]
Message-ID: <416C3857.9030109@sendmail.com> (raw)
In-Reply-To: <200410121210.15546.george@gentoo.org>
Hi George and all,
Thanks for the quick reply. I will post my next questions on gentoo-user
mailing list.
Though I wish to do something similar to the kde-base, that might not
solve the problem that I have.
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.
The kde-base has dependencies on the other kde-packages, and downloads
them "independently" from the download site,
as they are exposed "independently".
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.
Thanks again,
Ashish
George Shapovalov wrote:
>Hi Ashish.
>
>See kde-base/kde-xxx.ebuild. In short just put all these packages as
>dependencies into this "meta" package. Plus be sure to keep it in your
>overlay (see make.conf).
>
>Also, please use gentoo-user mailing list for questions such as this. This
>list is for discussions of portage development.
>
>George
>
>
>On Tuesday 12 October 2004 11:56, Ashish Gawarikar wrote:
>
>
>>Hello,
>>
>>I just started using gentoo a few days back, and I have started to like
>>it immensly. I like the emerge/ebuild packaging system.
>>I had a question in regards to packaging, I am planning to include
>>multiple ebuilds into one big ebuild and when I emerge that big ebuild,
>>it should emerge all the packages it contains. For example:
>>
>>dummy-1.0.0.ebuild contains
>>
>>foo-1.0.0.ebuild and
>>bar-1.0.0.ebuild
>>
>>I tried calling in the src_install of dummy-1.0.0.ebuild,
>>emerge foo-1.0.0.ebuild
>>but it gives access denied error saying trying to open_wr:
>>/var/log/emerge.log
>>
>>Is there a way I can achieve what I am trying to do.
>>
>>All the help is appreciated,
>>
>>Thanks in advance,
>>
>>Ashish Gawarikar
>>
>>--
>>gentoo-portage-dev@gentoo.org mailing list
>>
>>
>
>
>--
>gentoo-portage-dev@gentoo.org mailing list
>
>
>
--
gentoo-portage-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-10-12 20:05 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 [this message]
2004-10-12 20:37 ` George Shapovalov
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=416C3857.9030109@sendmail.com \
--to=ashish@sendmail.com \
--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