From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-14) on finch.gentoo.org X-Spam-Level: ** X-Spam-Status: No, score=2.1 required=5.0 tests=DMARC_REJECT,FROM_GOV_SPOOF, MAILING_LIST_MULTI,RDNS_NONE autolearn=no autolearn_force=no version=4.0.0 Received: from eyrie.gsfc.nasa.gov (unknown [128.183.203.3]) by chiba.3jane.net (Postfix) with ESMTP id 7A216AC50D for ; Mon, 29 Apr 2002 10:58:13 -0500 (CDT) Received: from eyrie.gsfc.nasa.gov (localhost.localdomain [127.0.0.1]) by eyrie.gsfc.nasa.gov (8.11.6/8.11.2) with ESMTP id g3TG0Sr20925 for ; Mon, 29 Apr 2002 12:00:49 -0400 Message-ID: <3CCD6E1C.C0576377@eyrie.gsfc.nasa.gov> Date: Mon, 29 Apr 2002 12:00:28 -0400 From: Bryan Muir X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.9-31 i686) X-Accept-Language: en MIME-Version: 1.0 To: gentoo-dev@gentoo.org References: <20020429150603.939E7AC4A8@chiba.3jane.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: [gentoo-dev] Multiplatform Portage. Sender: gentoo-dev-admin@gentoo.org Errors-To: gentoo-dev-admin@gentoo.org X-BeenThere: gentoo-dev@gentoo.org X-Mailman-Version: 2.0.6 Precedence: bulk Reply-To: gentoo-dev@gentoo.org List-Help: List-Post: List-Subscribe: , List-Id: Gentoo Linux developer list List-Unsubscribe: , List-Archive: X-Archives-Salt: 46e7272a-40f2-494f-8be0-d0905aeefee0 X-Archives-Hash: aa500aaf333bfda2be5c9d18e8799c90 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.