| 1 |
Hi, |
| 2 |
|
| 3 |
On Tuesday 20 May 2003 21:24, Paul de Vrieze wrote: |
| 4 |
> On Tuesday 20 May 2003 16:54, Stephan Hermann wrote: |
| 5 |
> > But I don't have a gentoo distribution as base linux. |
| 6 |
> > Company standard is debian and we have a split between OS administration |
| 7 |
> > and "application" administration. |
| 8 |
> > (application in the meaning of: software to run self coded products for |
| 9 |
> > customers) |
| 10 |
> > |
| 11 |
> > so I can't install the portage tree in /etc /usr/portage etc. I need to |
| 12 |
> > install it at /opt/apps/portage for example. |
| 13 |
> |
| 14 |
> Unfortunately most ebuilds presume that they are build on a gentoo system, |
| 15 |
> as such they have hardcoded directories. In general portage is not really |
| 16 |
> that suitable as a secondary package manager. |
| 17 |
|
| 18 |
I think you are misunderstanding. |
| 19 |
|
| 20 |
I'm not talking about ebuilds and gentoo software. I'm really talking about |
| 21 |
portage. |
| 22 |
|
| 23 |
Scenario: |
| 24 |
|
| 25 |
I want to build up a separate build server for own made profiles. |
| 26 |
I'm providing own ebuilds depending on self defined enviroments. |
| 27 |
I want to use portage, to manage different profiles. |
| 28 |
|
| 29 |
So, I have to move the portage python scripts from /usr/portage, the symlinks |
| 30 |
from /usr to somewhere else, and to redeclare all hardcoded path variables in |
| 31 |
the portage python source from e.g. /etc/make.conf to |
| 32 |
/opt/company_standard/portage_dist/etc/make.conf. |
| 33 |
|
| 34 |
I'm not talking about ebuilds, because I'm provinding my own set of ebuilds, |
| 35 |
specialised for several standard application enviroments. |
| 36 |
|
| 37 |
regards, |
| 38 |
|
| 39 |
\sh |
Archives