1 |
Procedure for using Portage in another distribution. |
2 |
|
3 |
I have been playing around with getting Portage to work in Redhat 7.1, |
4 |
and I haven't ironed |
5 |
out all the bugs yet, so I'll just outline what I have done so far. As |
6 |
usual, backup |
7 |
anything important before you try these instructions... |
8 |
I also attached these instructions to the bugzilla id: |
9 |
http://bugs.gentoo.org/show_bug.cgi?id=2215 |
10 |
|
11 |
1. Download portage source code. |
12 |
2. Untar into a work directory somewhere |
13 |
3. Download portage snapshot and untar into /usr |
14 |
4. cp portagexxx/bin/* to /usr/bin |
15 |
[Note: havent tracked down why this next step is necessary, but calling |
16 |
ebuild causes an |
17 |
error without it] |
18 |
4a. cp portagexxx/bin/ebuild* /usr/sbin |
19 |
5. cp portagexxx/cnf/* to /etc |
20 |
6. cp portagexxx/pym/* to /usr/local/lib/python2.2/site-packages/ |
21 |
7. cd to portagexxx/src/python-missongos and do python setup.py build |
22 |
8. do python setup.py install |
23 |
9. cd ../sandbox |
24 |
10. do make && make install |
25 |
[NOTE. the following step is crucial or it will disable about half of a |
26 |
redhat |
27 |
system] |
28 |
11. in etc, create an env.d directory. If you have a working gentoo |
29 |
system, |
30 |
grab the 00basic file and copy it to the new directory. This directory |
31 |
is what |
32 |
env-update uses to rebuild the ld.co.conf file. I modified the 00basic |
33 |
file so |
34 |
that it looked like the following: |
35 |
|
36 |
PATH=/usr/local/bin |
37 |
ROOTPATH=/usr/local/bin |
38 |
LDPATH=/usr/local/lib:/usr/lib:/usr/kerberos/lib:/usr/X11R6/lib:/usr/lib/sane:/usr/lib/qt-2.3.0/lib |
39 |
|
40 |
MANPATH=/usr/share/man |
41 |
INFODIR=/usr/share/info |
42 |
CVS_RSH=ssh |
43 |
PAGER=/usr/bin/less |
44 |
LESSOPEN="|lesspipe.sh %s" |
45 |
|
46 |
I could have made a seperate files, each with a different LDPATH line |
47 |
and they would have |
48 |
been merged, but I was feeling lazy. |
49 |
|
50 |
|
51 |
Conclusion: |
52 |
|
53 |
That should do it... the following are the caveats/problems that I |
54 |
havent solved yet... |
55 |
1. emerge rsync doesnt work as my place of employment has that port |
56 |
blocked. |
57 |
Additionally CVS access appears to be passworded. So I have to download |
58 |
the portage |
59 |
snapshots to update portage. |
60 |
|
61 |
2. Due to all the RPM's for the base system, portage always wants to |
62 |
emerge baselayout, |
63 |
etc... so for packages I have been using the --nodeps option and |
64 |
installing packages one |
65 |
at a time. The downside is that you have to install all required |
66 |
packages seperately. |
67 |
|
68 |
3. I was having the circular reference error, but without emerge rsync, |
69 |
I had to just |
70 |
emerge --nodeps python-fchksum and the error went away. |