From: Markus Brischke <zoke-gentoo@zoke.de>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] [ANN] Gentoo frequently unanswered questions (FUQ)
Date: Mon, 17 Jun 2002 23:47:16 +0200 [thread overview]
Message-ID: <20020617214716.GA30108@Q.math.fu-berlin.de> (raw)
In-Reply-To: <1024073640.18736.54.camel@red.ces.clemson.edu>
Quoting Grant Goodyear (g2boojum@gentoo.org):
> > Another (yet unanswered) question for myself could be:
> >
> > How can i manage my own ebuildfiles/packages without destroying them by (r)sync?
> >
> > I am looking for an elegant way to manage my (own) testingpackages and
> > packages which are not part of gentoo yet :) Any clues?
>
> Yep. Take a look at the FAQ; I just added your question and a
> moderately detailed answer.
Thanks. Using cvs is one good method. I thought about a bit the problem.
Another solution is a symbolic link to the local directory given in
categories.
So it may be easy to do the following in the first step. Integrate local
in the "master" categories and set a symbolic link local. Then you can
use the rsynccommand with --safe-links (only if the directory behind
local is placed outside which is in this case the only logic).
This all is imho only a cludge. Imho we should think about how to
integrate userdefined ebuild-files more smoothly.
Ways doing this could be:
- Creating something like PORTAGE_PATH
- making a config file for categories in /etc and inherit all the
different categories (problem is the outside PORTDIR thing. But i
didn't understand why an ebuildfile explicitly defined fullpath must
be inside PORTDIR (question for the faq? ;))).
- making a subdir prestine and syncing only this (but the
categoriesproblem is still to be solved here).
But in this case i think cvs is the right answer, because making diffs
is more easy :)
Have fun.
Markus
next prev parent reply other threads:[~2002-06-17 21:47 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
2002-06-14 12:33 ` Francisco Gimeno
2002-06-14 16:54 ` Grant Goodyear
2002-06-17 21:47 ` Markus Brischke [this message]
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=20020617214716.GA30108@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