bash-2.05b# ./Portage
./Portage: line 7: : command not found
./Portage: line 11: : command not found
./Portage: line 13: : command not found
./Portage: line 19: : command not found
./Portage: line 27: : command not found
./Portage: line 36: syntax error near unexpected token `then'
./Portage: line 36: ` if [ ! -f portage-2.0.50-r1.tar.bz2 ];then '
bash-2.05b#

I guess there is a good reason for this - probably because I didn't understand the other stuff you wrote. (Hey kill me if you want - but I admit I'm not a programmer).

I just want to learn how to do it this once - and if I get it going no matter what distro I am using, I think I will always use Portage.

does the above code cut and pasted directly into a shell, execute? now cut and paste the same thing into a file and execute the file like "/bin/bash -c <filename>", post the results. post the output of "echo $SHELL" as well.

Dude I will do it tomorrow I promise. It's too late now. But I really do hope you check back. I mean once I get this done - like I said it doesn't matter what distro I use any more - I will always be able to run portage.

I wish there was just some kind of standard Gentoo install I could use like a stage 5 or 6 with full GUI etc so I wouldn't need to do stuff like this. Oh well I guess people have been asking for this for a long time.

I don't know how slackware builds its bash, but one thing is for sure: either the text contains garbage (which editor are you using?) or the installed bash is screwed up, because same text runs fine on my machine.

From the errors, with the bash you have, you won't be able to use portage even if you could get it installed somehow because ebuild.sh (a shell script which portage uses to build packages) uses the same syntax and it will fail with similar "command not found" errors.

I think I am running out of ideas here...may be somebody who knows bash on slackware better, might comment here.

try to find out what options did the slackware install the bash with...post output of:

Ahh NM I just copied and pasted the text into a conole using nano and it executed cleanly.

Sor we are all sorted now, the only thing is I got a warning message about:

Code:

!!! /etc/make.profile is not a symlink and will probably prevent most merges.
!!! It should point into a profile within /usr/portage/profiles/
!!! (You can safely ignore this message when syncing. It's harmless.)

I guess then because I am merging for the first time (or at least the script does this?) that I can safely ignore this?

Also it keeps crapping out during emerge sync with:

Code:

!!! /etc/make.profile is not a symlink and will probably prevent most merges.
!!! It should point into a profile within /usr/portage/profiles/
!!! (You can safely ignore this message when syncing. It's harmless.)-

/usr/sbin/ebuild.sh: line 64: einfo: command not found
/usr/sbin/ebuild.sh: line 238: einfo: command not found
/usr/sbin/ebuild.sh: line 327: eend: command not found
/usr/sbin/ebuild.sh: line 238: einfo: command not found
/usr/sbin/ebuild.sh: line 327: eend: command not found
/usr/sbin/ebuild.sh: line 238: einfo: command not found
/usr/sbin/ebuild.sh: line 327: eend: command not found

Well for some reason my init.d file in Slackware got deleted. I'm not sure how - it was there before I started messing with portage. But anyway I restored it from a back up and ran the script again - so both those shortcuts are now there. Unfortunately it is still borking on libtools. Moreover an awful lot of stuff I would like to get from portage (KDE 3.2, Mozilla 1.6 and many others) all seem to depend very heavily on this libtools package.

I know from my experiences with Gentoo in the past that portage can get stuck like this on certain packages - but it is odd that is should happen so early - and specifically as a part of the process of installing and updating portage itself.

Maybe its about use flags? Do I need and specific flags set to use libtools?

there are packages(gcc, glibc, binutils, baselayout) you should never emerge and should have them injected. make sure you read the first post in this thread carefully.

post your libtool errors...gentoo has a certain way of doing automake/autoconf whereby it points automake executable to shell script which calls 1.4 version by default and expects WANT_AUTOMAKE environment variable set if you want to use 1.78 or later. ||ly for autoconf. so, its not a bug.

you should emerge m4, automake, autoconf and libtool before you start using portage full time. REMEMBER THAT ITS GOING TO OVERWRITE your existing auto* tools, so make up your mind about proceeding with portage all the way.

post output of "emerge zlib"...that should be safest to do w/o any changes.

Well just to be clear portage began downloading and updating a bumch of stuff while the script was running - so I had no control over whether to use it or not. I understand what you said about setting up exclusions - but I wonder if any harm was caused because portage downloaded a bunch of stuff during the install process anyway? Is it perhaps possible to set up your script so that it automatically set exclusions on files for non gentoo distributions that probably should never be updated by portage?

In any case I am still stuck on the part of the script where - without my intervention - it and/or portage attempts to download and install libtools.

You see I am simply waiting for the script to finish completing all the tasks that it set out to accomplish - I am not yet myself trying to use portage - nor am I able to, since if I try to emerge anything it simply tries to start emerging libtools again.

I think maybe we are not that far off with a solution - but what that solution might be currently escapes me.

script does inject the packages it considers unsafe(those fabfour). you should do emerge -p <packagename> before any merge. you can check if those packages are already injected or not and then inject them.

you have to emerge these four in that order: m4, automake, autoconf and libtool to get past the libtool issue.

You did emerge zlib successfully.

emerge inject takes argument like "sys-libs/zlib-1.1.4-r2". That means, you do a "emerge -p gcc" first, see the output and emerge inject that. e.g.

just inject pam, pam-login, shadow, cronbase, python, perl, xfree for now and see what it returns for "emerge -p portage"....it should be pretty minimal stuff.

portage is still not installed. once portage installs properly, you can emerge those.

I didn't have this much trouble running this script and getting portage to work even on Solaris.

Since you are kickstarted by now, at this moment, I would strongly suggest to read man pages on "portage", "emerge", "ebuild". You gonna need to know each one of these in-and-out to get portage working correctly...and keeping it that way.

keep posting your problems here though...I will be more than happy to help you.