From: Bryan Muir <bmuir@eyrie.gsfc.nasa.gov>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Multiplatform Portage.
Date: Mon, 29 Apr 2002 12:00:28 -0400 [thread overview]
Message-ID: <3CCD6E1C.C0576377@eyrie.gsfc.nasa.gov> (raw)
In-Reply-To: 20020429150603.939E7AC4A8@chiba.3jane.net
Procedure for using Portage in another distribution.
I have been playing around with getting Portage to work in Redhat 7.1,
and I haven't ironed
out all the bugs yet, so I'll just outline what I have done so far. As
usual, backup
anything important before you try these instructions...
I also attached these instructions to the bugzilla id:
http://bugs.gentoo.org/show_bug.cgi?id=2215
1. Download portage source code.
2. Untar into a work directory somewhere
3. Download portage snapshot and untar into /usr
4. cp portagexxx/bin/* to /usr/bin
[Note: havent tracked down why this next step is necessary, but calling
ebuild causes an
error without it]
4a. cp portagexxx/bin/ebuild* /usr/sbin
5. cp portagexxx/cnf/* to /etc
6. cp portagexxx/pym/* to /usr/local/lib/python2.2/site-packages/
7. cd to portagexxx/src/python-missongos and do python setup.py build
8. do python setup.py install
9. cd ../sandbox
10. do make && make install
[NOTE. the following step is crucial or it will disable about half of a
redhat
system]
11. in etc, create an env.d directory. If you have a working gentoo
system,
grab the 00basic file and copy it to the new directory. This directory
is what
env-update uses to rebuild the ld.co.conf file. I modified the 00basic
file so
that it looked like the following:
PATH=/usr/local/bin
ROOTPATH=/usr/local/bin
LDPATH=/usr/local/lib:/usr/lib:/usr/kerberos/lib:/usr/X11R6/lib:/usr/lib/sane:/usr/lib/qt-2.3.0/lib
MANPATH=/usr/share/man
INFODIR=/usr/share/info
CVS_RSH=ssh
PAGER=/usr/bin/less
LESSOPEN="|lesspipe.sh %s"
I could have made a seperate files, each with a different LDPATH line
and they would have
been merged, but I was feeling lazy.
Conclusion:
That should do it... the following are the caveats/problems that I
havent solved yet...
1. emerge rsync doesnt work as my place of employment has that port
blocked.
Additionally CVS access appears to be passworded. So I have to download
the portage
snapshots to update portage.
2. Due to all the RPM's for the base system, portage always wants to
emerge baselayout,
etc... so for packages I have been using the --nodeps option and
installing packages one
at a time. The downside is that you have to install all required
packages seperately.
3. I was having the circular reference error, but without emerge rsync,
I had to just
emerge --nodeps python-fchksum and the error went away.
next parent reply other threads:[~2002-04-29 15:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020429150603.939E7AC4A8@chiba.3jane.net>
2002-04-29 16:00 ` Bryan Muir [this message]
2002-04-27 8:00 [gentoo-dev] Multiplatform Portage Tristan Ball
2002-04-29 5:22 ` Craig Joly
2002-04-29 5:35 ` Arcady Genkin
2002-04-30 15:27 ` maarten
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=3CCD6E1C.C0576377@eyrie.gsfc.nasa.gov \
--to=bmuir@eyrie.gsfc.nasa.gov \
--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