An emerge wrapper for breaking emerges into chunks

hielvc · Posted: Sun Jun 05, 2005 5:14 pm Post subject:

Here is my suggestion. I wouldnt put this in /usr/bin or /usr/local/bin at this
time. I would put it and basesys-build.lst in /root or a directory in /root. To
run it " cd directory && sh sys-build.sh -b " or to see what it thinks its gonna do
" cd directory && sh sys-build.sh -p ". "-pb " does the same as " -p ". Why,
because this is a work in progress and I dont like putting basesys-build.lst in
/usr/bin or /usr/local/bin. Yes you can edit the script to change the name of
basesys-build.lst and its location.

Ok cut and pasted the sys-build.sh and it worked. Did you use an editor or did
you use a word processor, abiword kde_do_all OpenOffice_Word ? For those who arent
aware of this for a program you need to use kate, gedit, nano, vi ,vim ,gvim,
scite, nedit and/or joe, these are editors. Anyway Ill post a link today to a tar
file of sys-build.sh and basesys-build.lst.
_________________
An A-Z Index of the Linux BASH command line

southpaw · Posted: Sun Jun 05, 2005 7:06 pm Post subject:

Hey hielvc,
Forgive me for asking this, but I'm a little confused as to how I properly run this script. I mean I followed your instructions on page one, I downloaded the latest version, then I pasted it into my editor, etc...etc....but I'm not getting anything. I was just wondering if you could point me in the right direction on how to get this script running correctly?? Any advice would be much appreciated, thanx
_________________
Legalize It

hielvc · Posted: Sun Jun 05, 2005 8:23 pm Post subject:

Which script ?
_________________
An A-Z Index of the Linux BASH command line

southpaw · Posted: Sun Jun 05, 2005 9:55 pm Post subject:

...emwrap.sh...

_________________
Legalize It

hielvc · Posted: Sun Jun 05, 2005 10:56 pm Post subject:

emwrap.sh -suDp ==> emerge system -uDp The -p is the same as -p in emerge PRETEND shows you what its going to do, but doesnt do it.
emwrap.sh -suD ==> emerge system -uD will not build any of the TC items
emwrap.sh -suDtp ==> emerge system -uDp but TC items only, wont build anything but the TC items that have updates. gcc and binutils and their config files only.( Depends on which build chain the item falls in.) Used with "p" it shows what it will build. -w stands for world. So
emwrap.sh -wuDp is a world update. Now if you want to do the TC update and any other files to be updated "-b " , both, it builds the TC items first then the other files. Now if you want rebuild the whole shooting match "-e" , --emptytree, if used -t rebuilds the entire TC, with -b the TC and system or world depending on if you used -ste or -sbe or -wet or -web and this works to -ebs.

If emwrap.sh doesnt run period then try, in the same directory that you put it " sh emwrap.sh " and you should get the help print out. If that works then you need to "chmod 777 emwrap.sh ". Hope that helps.
_________________
An A-Z Index of the Linux BASH command line

hielvc · Posted: Sun Jun 05, 2005 11:04 pm Post subject:

Posted links to basesys-build.sys and sys-build.sh at the top of page 1.
_________________
An A-Z Index of the Linux BASH command line

southpaw · Posted: Mon Jun 06, 2005 5:24 am Post subject:

Well hielvc,
I opened the script up in nano and then I saved it under /usr/bin/emwrap.sh, then I opened up eterm and issued the command

tabascoz · Posted: Mon Jun 06, 2005 5:10 pm Post subject:

Hi hielvc

hielvc · Posted: Tue Jun 07, 2005 12:50 am Post subject:

Its a bug Dang it. Ill try to get it fixed tonight . The only way around it is to copy "buildsys-build.lst to basesys-build.org and then open up basesys-build.lst in an editor and delete everthing thats been built and then restart sys-build.sh. Then " cp basesys-build.org basesys-build.lst ".
_________________
An A-Z Index of the Linux BASH command line

hielvc · Posted: Tue Jun 07, 2005 2:20 am Post subject:

Ok the -r or resume in sys-build.sh is fixed and is now posted and updated on the download link.

It works but the total count when you restart is off, it gives the original total but if you check out what its building youll see it isnt starting wtih portage. Oh if you wonder why its first its to get that complianing whining prog outta da way :wink:

_________________
An A-Z Index of the Linux BASH command line

tabascoz · Posted: Tue Jun 07, 2005 3:57 am Post subject:

Thanks Hielvc!

i will try it now :D

Naveg · n00b Joined: 20 May 2005 Posts: 73

Hey,

I found this through the updating after a 1/3 install page...and i'm wondering: what's the difference between the two provided scripts...and what does each do

hielvc · Posted: Fri Jun 10, 2005 3:05 am Post subject:

tcupdate.sh and emwrap.sh do basicly the same thing. Tcudate.sh is not being maintaned at the moment. I think that emwrap.sh does a more complete job of rebuilding the entire system and then world.

sys-build.sh is new and once fully tacked down will be used in place of the current emwrap.sh -db.
_________________
An A-Z Index of the Linux BASH command line

Naveg · n00b Joined: 20 May 2005 Posts: 73

will this tell me what its going to update and ask if i wish to continue?

hielvc · Posted: Sat Jun 11, 2005 4:18 pm Post subject:

See 9 post up.
_________________
An A-Z Index of the Linux BASH command line

southpaw · Posted: Wed Jun 22, 2005 10:11 am Post subject:

hey hielvc,
Something weird has been happening every time I use "sh emwrap.sh -suD", this is what I've been getting...

hielvc · Posted: Wed Jun 22, 2005 1:48 pm Post subject:

Yes its a standard " emerge message ". Basically pkg1 requires a specfic usually higher version of pkg2 before it can install. In this case both progs gnome-themes and gtk-engines are blocking each other. , so you have to remove the progs useing " emerge --unmerge prog1 prog2 " then continue with your update and the newer versions will be installed. Whenever you do this do a dry run " emerge --unmerge .......... -p " first.
_________________
An A-Z Index of the Linux BASH command line

heavyt

Hielvc I am confuse with two of your posts. I have posted them below. My question is do we need the two scripts on page 6 if we do what you told segin to do in the first post below or do we still need to use the two scripts on page 6 to deal with lib problem? Thanks for your time and effort.

Posted: Thu Jun 23, 2005 11:43 am Post subject:

hielvc · Posted: Fri Jun 24, 2005 7:22 am Post subject:

First choice get sys-build.sh and basesys-build.lst and emwrap.sh. Then

heavyt · Posted: Fri Jun 24, 2005 12:47 pm Post subject:

Thank you

taipan67 · Posted: Fri Jun 24, 2005 5:47 pm Post subject:

If you see this yourself, hielvc, you may recall helping me out on another thread yesterday, regarding gcc-config internal logic...

I'm here now because i've started from scratch with a variation on Bob P's Stage 1/3 install, hopefully utilising 'emwrap.sh'

The reasons for my using a Stage 1 install have been made redundant by the changes in 2005.0, as i now know... :oops:

I've downloaded 'emwrap.sh version 3.0.2', & i have a couple of questions for you, & any other readers who can help, before i "light the blue touch-paper":-

First, the 'verbose' option doesn't appear to work, as it would with 'emerge'. My impression from the 'help' is that it should be available, which i would love, as i'm an avid user of '-pv' :roll:

Second, your script & Bob P's Guide for 2005.0 & GCC-3.4.4 have differing opinions about whether or not 'libstdc++-v3' constitutes an integral component of the toolchain. I'd like to hear the reasoning behind this...

Lastly, as we speak i have not done the initial toolchain-upgrade, & before running the script to do so, i'd like to clarify whether i'd be best advised to use Bob P's suggested 'emerge gcc-config glibc binutils libstdc++-v3 gcc' first, then run the script, by which method i could use conservative FLAGS while the 3.3.5 compiler is building the new one, then go crazy once i've switched to 3.4.4 :twisted:

Any & all help will be enormously appreciated... :wink:

EDIT: Here's something that caused me to raise an eyebrow... After my previous, screwy install, i saved all of the source tarballs that were downloaded during the completed 'emerge -e system', yet when i just ran 'emerge -pv gcc-config glibc binutils libstdc++-v3 gcc', i still needed to download 23Mb for 'libstdc++-v3'... Could that be where everything went tits up before. :?:

EDIT2: I may have discovered something about the previous install - can i draw your attention to this post without being too cheeky?
_________________
"Anyone who goes to see a psychiatrist should have their head examined!"

Bob P · Posted: Fri Jun 24, 2005 9:08 pm Post subject:

gcc 3.4.3 used to pull in libstdc++-v3 as a dependency. gcc 3.4.4 doesn't. there's your answer.
_________________
.
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks

hielvc · Posted: Sat Jun 25, 2005 12:53 am Post subject:

1. I happen to find out the "v" option wasnt working myself last night. After some thought I removed it, as between the output of emwrap + -v there would be to much cluter. It would be easier to run run " emerge -v " AND I wouldnt have to worry about filtering all that gaaabage out. Oh posted new Version 3.0.4 removeing -v, and the script now cleans up after it self now.

2 Thanks Bob, you Jackass

3 The primary difference useing "emwrap.sh -set" and the guide is that since --emptytree says everthing needs to be rebuilt it builds linux-headers glibc gcc-config binutils-config binutils gcc glibc binutils gcc. I did the same thing about 5 months ago and I just used Bobs one liner for that first rebuild. Then I set up CFLAGS and USE and then I used emwrap. <Begin Rant> Why, because "emerge system -e" still builds the TC ass bakwards.

First 24 lines of "emerge system -e". The tc build order

Quote:

zlib, ncurses, bash, readline, binutils, gcc, linux-headers glibc

Hey Bob or moacha why dont you make a oneliner that builds the TC that way :?:

Because its totally wrong and if a person hasnt updated for 4 to 6 months it could easily break their system. The thing is until you present it this way you dont realize just how dangerous and wrong it is. The other files I listed are either run time deps of glibc and/or important progs for the system. The only reason that it works is because of the TC oneliner that you do before it. <end rant> The other thing about this that its supose to 1 nail down your TC, it doesnt, and rebuild everything with your "nailed down TC". What is really curious is that it seems to work. That begs the question of HOW and WHY which is what I'm addressing in a rewrite of the front page of this thread.

So you could use " emwrap.sh -seb" which builds TC twice and then emerges everything everything else. or I would do this

Code:

emerge linux-headers glibc binutils gcc && emwrap -se

This nails down the TC and rebuilds the rest of the system files with it.

Off to look at your other post and then I have to finish the front page rewrite that goes into more depth about the "emerge system..system..world ..world" bull dinkle :!:

_________________
An A-Z Index of the Linux BASH command line

taipan67 · Posted: Sat Jun 25, 2005 3:24 am Post subject:

Cheers hielvc, i've posted some interesting reading here - i'd greatly appreciate your insight... :roll:

_________________
"Anyone who goes to see a psychiatrist should have their head examined!"