From: Markus Brischke <zoke-gentoo@zoke.de>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] [ANN] Gentoo frequently unanswered questions (FUQ)
Date: Fri, 14 Jun 2002 13:16:39 +0200 [thread overview]
Message-ID: <20020614111639.GA25049@Q.math.fu-berlin.de> (raw)
In-Reply-To: <200206140510.10862.cedric@neopeak.com>
Quoting Cedric Veilleux (cedric@neopeak.com):
> Hi,
>
> There are probably may ways to achieve this, but what I prefer is to create
> a portage tree in my home directory with my ebuilds. Something like
> portage/distfiles/somepackage.tar.gz
> portage/net-mail/qmail-hack/qmail-hack-1.0.ebuild
> ...
>
> Then all I have to do is "tar xzf myports.tar.gz portage" and then I can
> distribute the tarball or extract it in my own portage tree. I don't care if
> an emerge --clean rsync deletes it since I can easily re-extract it later..
Thanks for your answer. That is a possible solution, but i think it's
not really elegant, because you keep the same data twice. Also if you
have the "master" ebuildfiles in your home and you do a change you have
always to copy the into the portage tree.
In a first view i thought about making similar symlinks. But that is not
elegant either. What i will soon test is to put the official tree into a
special directory and only this one will be synced. I will soon comment
this :)
Thanks for all
Markus
next prev parent reply other threads:[~2002-06-14 11:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-14 6:58 [gentoo-dev] [ANN] Gentoo frequently unanswered questions (FUQ) Mecho Puh
2002-06-14 8:58 ` Markus Brischke
2002-06-14 5:10 ` Cedric Veilleux
2002-06-14 11:16 ` Markus Brischke [this message]
2002-06-14 12:33 ` Francisco Gimeno
2002-06-14 16:54 ` Grant Goodyear
2002-06-17 21:47 ` Markus Brischke
2002-06-17 3:51 ` [gentoo-dev] " Mecho Puh
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=20020614111639.GA25049@Q.math.fu-berlin.de \
--to=zoke-gentoo@zoke.de \
--cc=gentoo-dev@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