1 |
Quoting Grant Goodyear (g2boojum@g.o): |
2 |
> > Another (yet unanswered) question for myself could be: |
3 |
> > |
4 |
> > How can i manage my own ebuildfiles/packages without destroying them by (r)sync? |
5 |
> > |
6 |
> > I am looking for an elegant way to manage my (own) testingpackages and |
7 |
> > packages which are not part of gentoo yet :) Any clues? |
8 |
> |
9 |
> Yep. Take a look at the FAQ; I just added your question and a |
10 |
> moderately detailed answer. |
11 |
|
12 |
Thanks. Using cvs is one good method. I thought about a bit the problem. |
13 |
Another solution is a symbolic link to the local directory given in |
14 |
categories. |
15 |
|
16 |
So it may be easy to do the following in the first step. Integrate local |
17 |
in the "master" categories and set a symbolic link local. Then you can |
18 |
use the rsynccommand with --safe-links (only if the directory behind |
19 |
local is placed outside which is in this case the only logic). |
20 |
|
21 |
This all is imho only a cludge. Imho we should think about how to |
22 |
integrate userdefined ebuild-files more smoothly. |
23 |
|
24 |
Ways doing this could be: |
25 |
- Creating something like PORTAGE_PATH |
26 |
- making a config file for categories in /etc and inherit all the |
27 |
different categories (problem is the outside PORTDIR thing. But i |
28 |
didn't understand why an ebuildfile explicitly defined fullpath must |
29 |
be inside PORTDIR (question for the faq? ;))). |
30 |
- making a subdir prestine and syncing only this (but the |
31 |
categoriesproblem is still to be solved here). |
32 |
|
33 |
But in this case i think cvs is the right answer, because making diffs |
34 |
is more easy :) |
35 |
|
36 |
Have fun. |
37 |
|
38 |
Markus |