Mailing List Archive

Den 2012-06-04 15:23, Daiajo Tibdixious skrev:
> I know when I do an emerge world it looks at /var/lib/portage/world
> for the list of packages.
> I went looking for a 'system' list for the emerge system command &
> did
> not find it.

emerge -pe system | xargs -- less

or something ? :=)

my own fav is:

qlist -IC dev-php/pecl-* | xargs -- emerge -1

call it reemergetree.sh

dont parse files on your own, use portage

Daiajo Tibdixious writes:

> I know when I do an emerge world it looks at /var/lib/portage/world
> for the list of packages.
> I went looking for a 'system' list for the emerge system command & did
> not find it.
> I also looked in make.profile and didn't find anything likely.
> I also googled my query but got too many spurious matches.
> I'm sure there is a simple answer.

No, I don't think so. There's the /usr/portage/profiles/base/packages
file, which is somewhat similar to /var/lib/portage/world, but the exact
list depends on your profile.

> I want to write a script that reads the system list, finds the
> binpkg's, and copies the latest to backup.
> I can do this easy for the world list.

Then this should do it: emerge -ep system | awk '{print $4}'

Wonko

On Mon, Jun 4, 2012 at 10:11 AM, Alex Schuster <wonko@wonkology.org> wrote:
> Daiajo Tibdixious writes:
>
> No, I don't think so. There's the /usr/portage/profiles/base/packages
> file, which is somewhat similar to /var/lib/portage/world, but the exact
> list depends on your profile.

The others that have suggested using portage tools to obtain the
system set are worth listening to.

The actual lists are in a bunch of files in your profile. However,
profiles are nested, so you need to check the packages file for your
profile, its parents, their parents, and so on. The files are also
commented and such, so relying on already-debugged code is wise.

Rich

On Mon, Jun 4, 2012 at 6:23 AM, Daiajo Tibdixious <daiajo@gmail.com> wrote:
> I know when I do an emerge world it looks at /var/lib/portage/world
> for the list of packages.
> I went looking for a 'system' list for the emerge system command & did
> not find it.
> I also looked in make.profile and didn't find anything likely.
> I also googled my query but got too many spurious matches.
> I'm sure there is a simple answer.
>
> I want to write a script that reads the system list, finds the
> binpkg's, and copies the latest to backup.
> I can do this easy for the world list.
> --
> Daiajo Tibdixious daiajo@gmail.com
>

With the newer versions of portage (2.2.x) you can do

emerge -pve @system

On my box it returned a result of 439 packages. Seems high, but...

You can temporarily move /var/lib/portage/world to some other name.
With the world file gone there's nothing to install to satisfy the
@world set. With this setup I did

emerge -pve @world

and got a result of 439 package, so at least there is agreement.

Now, I don't truly believe all of these 439 packages are necessary to
complete @system as my 32-bit Gentoo VM only has 174 packages in
@world.

Go figure, and don't forget to move the world file back again... ;-)

HTH,
Mark

On Tue, Jun 5, 2012 at 12:40 AM, Mark Knecht <markknecht@gmail.com> wrote:
> On Mon, Jun 4, 2012 at 6:23 AM, Daiajo Tibdixious <daiajo@gmail.com> wrote:
>> I know when I do an emerge world it looks at /var/lib/portage/world
>> for the list of packages.
>> I went looking for a 'system' list for the emerge system command & did
>> not find it.
>> I also looked in make.profile and didn't find anything likely.
>> I also googled my query but got too many spurious matches.
>> I'm sure there is a simple answer.
>>
>> I want to write a script that reads the system list, finds the
>> binpkg's, and copies the latest to backup.
>> I can do this easy for the world list.
>> --
>> Daiajo Tibdixious daiajo@gmail.com
>>
>
> With the newer versions of portage (2.2.x) you can do
>
> emerge -pve @system
>
> On my box it returned a result of 439 packages. Seems high, but...
>
> You can temporarily move /var/lib/portage/world to some other name.
> With the world file gone there's nothing to install to satisfy the
> @world set. With this setup I did
>
> emerge -pve @world
>
> and got a result of 439 package, so at least there is agreement.
>
> Now, I don't truly believe all of these 439 packages are necessary to
> complete @system as my 32-bit Gentoo VM only has 174 packages in
> @world.
>
> Go figure, and don't forget to move the world file back again... ;-)
>
> HTH,
> Mark
>
ty all, I forgot about the dependent packages. I might forget about
separating system & world & just backup all the binpkg's

Daiajo Tibdixious posted on Tue, 05 Jun 2012 09:52:15 +1000 as excerpted:

> I forgot about the dependent packages. I might forget about separating
> system & world & just backup all the binpkg's

FWIW, that's pretty much what I do here (but with all packages together,
not separate @system/@world). I use FEATURES=binpkg and have a separate
binpkgs partition, then a second partition of the same size that I mkfs
and copy everything from the first one to, every so often.

Binpkg partition size is now 8 gigs. 3 gigs works if you clean out all
the old binpkgs regularly (eclean), and I ran 4 gigs for awhile, but I
run the kde betas (as of yesterday, 4.8.80 aka 4.9-beta1) and like to
keep plenty of room for the last upstream-stable I had (4.8.3) plus the
last and current betas, and found 4 gig a bit tight for that, so when I
upgraded disks, I doubled the size to 8 gigs, tho 6 probably would have
done as well.

It doesn't matter so much on a packages partition as the files are large,
but FWIW I run reiserfs with tail-packing on, as I can't see wasting all
the partial blocks, and reiserfs has been quite stable for me (even thru
hardware issues) since data=ordered mode was introduced back in 2.6.16 or
so. It makes a BIG difference on the sources (both gentoo/overlay trees
and kernel, plus ccache) partition, tho. (I'm looking forward to the
still experimental btrfs, but tried it recently and it's not solid yet,
particularly in the case of hard-reboots, etc. Lost files is NOT my
thing, and missing parts of files or having files replaced with the
contents of other files is worse, hard reboot or no hard reboot, so it
was back to the tried and tested, for me.)

FWIW, I use the dup-partition thing for everything. Put it on raid1
(again, looking forward to btrfs raid1 mode) if you have it, so losing a
disk won't kill things either, and you're set for either loss of disk
(raid1) or fat-fingering something (backup partition). Three copies of
root (working and two backups), in case both the working and a backup go
down while I'm doing maintenance, two of everything else.

(If you have multiple disks in md/raid1 or similar, making /boot a normal
partition or a raid1 of half the drives if more than two, with its backup
a similar partition on the other drive(s), works well. Select which one
you want to boot in bios, and upgrade one at a time then test before
upgrading the other, when doing bootloader upgrades. That works well for
git kernels too, only upgrading the backup /boot with full kernel
releases, keeping the git kernels on the working /boot. If just a single
disk, than obviously more than one /boot doesn't help that much since the
initial sector bootloader can only point to one /boot.)

--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman

On Tue, Jun 5, 2012 at 1:42 PM, Duncan <1i5t5.duncan@cox.net> wrote:
> Daiajo Tibdixious posted on Tue, 05 Jun 2012 09:52:15 +1000 as excerpted:
>
>> I forgot about the dependent packages. I might forget about separating
>> system & world & just backup all the binpkg's
>
> FWIW, that's pretty much what I do here (but with all packages together,
> not separate @system/@world).  I use FEATURES=binpkg and have a separate
> binpkgs partition, then a second partition of the same size that I mkfs
> and copy everything from the first one to, every so often.
>
> Binpkg partition size is now 8 gigs.  3 gigs works if you clean out all
> the old binpkgs regularly (eclean), and I ran 4 gigs for awhile, but I
> run the kde betas (as of yesterday, 4.8.80 aka 4.9-beta1) and like to
> keep plenty of room for the last upstream-stable I had (4.8.3) plus the
> last and current betas, and found 4 gig a bit tight for that, so when I
> upgraded disks, I doubled the size to 8 gigs, tho 6 probably would have
> done as well.

> --
> Duncan - List replies preferred.   No HTML msgs.
> "Every nonfree program has a lord, a master --
> and if you use the program, he is your master."  Richard Stallman
>
>

I got FEATURES=buildpkg already, and run eclean regularly, and
planning to back up to 8G USB drive, so should work.

I only have the 1 drive. My case doesn't have enough power plugs for
more than 1. :(
so no raid for me. (No rich enough for a better 1)

Daiajo Tibdixious posted on Tue, 05 Jun 2012 15:11:43 +1000 as excerpted:

> I only have the 1 drive. My case doesn't have enough power plugs for
> more than 1. :(
> so no raid for me. (No rich enough for a better 1)

Ugh, money issues here too, ATM.

But if it's just the power plug, no problem. Splitters are available.
Data connections are different, tho. If you're out of those, you're out,
unless you have a PCI(E) slot to stick an expansion card in, and if
you're out of those too... And of course if your power supply simply
doesn't have the power to spare... but 2.5 inch drives tend to be power
sippers as they're designed for battery use, and if you're running /that/
close to the edge, power-wise, you're risking instability anyway.

But of course hard drives themselves cost money, and if things are as
tight for you as they are for me right now...

But it's nice if you have the few extra $$ for it...

--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman