[gentoo-user] gentoo

[gentoo-user] gentoo

[Joseph]

After recent emerge I get few blockers, that I don't know what to do with it
My box has not been updated for 3-months :-/


* Error messages for package dev-perl/glib-perl-1.301.0:

 * ERROR: dev-perl/glib-perl-1.301.0::gentoo failed (configure phase):
 *   Unable to build!
 *
 * Call stack:
 *     ebuild.sh, line   93:  Called src_configure
 *   environment, line 2371:  Called perl-module_src_configure
 *   environment, line 1979:  Called perl-module_src_prep
 *   environment, line 2051:  Called die
 * The specific snippet of code:
 *               perl Makefile.PL "$@" <<< "${pm_echovar}" || die
"Unable to build!";
 *
 * If you need support, post the output of `emerge --info
'=dev-perl/glib-perl-1.301.0::gentoo'`,
 * the complete build log and the output of `emerge -pqv
'=dev-perl/glib-perl-1.301.0::gentoo'`.
 * The complete build log is located at
'/var/log/portage/dev-perl:glib-perl-1.301.0:20140915-235806.log'.
 * For convenience, a symlink to the build log is located at
'/var/tmp/portage/dev-perl/glib-perl-1.301.0/temp/build.log'.
 * The ebuild environment file is located at
'/var/tmp/portage/dev-perl/glib-perl-1.301.0/temp/environment'.
 * Working directory:
'/var/tmp/portage/dev-perl/glib-perl-1.301.0/work/Glib-1.301'
 * S: '/var/tmp/portage/dev-perl/glib-perl-1.301.0/work/Glib-1.301'

 * Error messages for package dev-perl/DBD-mysql-4.20.0-r1:

 * ERROR: dev-perl/DBD-mysql-4.20.0-r1::gentoo failed (configure phase):
 *   Unable to build!
 *
 * Call stack:
 *     ebuild.sh, line   93:  Called src_configure
 *   environment, line 2370:  Called perl-module_src_configure
 *   environment, line 1977:  Called perl-module_src_prep
 *   environment, line 2049:  Called die
 * The specific snippet of code:
 *               perl Makefile.PL "$@" <<< "${pm_echovar}" || die
"Unable to build!";
 *
 * If you need support, post the output of `emerge --info
'=dev-perl/DBD-mysql-4.20.0-r1::gentoo'`,
 * the complete build log and the output of `emerge -pqv
'=dev-perl/DBD-mysql-4.20.0-r1::gentoo'`.
 * The complete build log is located at
'/var/log/portage/dev-perl:DBD-mysql-4.20.0-r1:20140916-001541.log'.
 * For convenience, a symlink to the build log is located at
'/var/tmp/portage/dev-perl/DBD-mysql-4.20.0-r1/temp/build.log'.
 * The ebuild environment file is located at
'/var/tmp/portage/dev-perl/DBD-mysql-4.20.0-r1/temp/environment'.
 * Working directory:
'/var/tmp/portage/dev-perl/DBD-mysql-4.20.0-r1/work/DBD-mysql-4.020'
 * S: '/var/tmp/portage/dev-perl/DBD-mysql-4.20.0-r1/work/DBD-mysql-4.020'

 * Error messages for package net-print/cups-1.7.3:

 * Your usb printers will be managed via libusb. In this case,
 * cups-1.7.3 requires the USB_PRINTER support disabled.
 * Please disable it:
 *     CONFIG_USB_PRINTER=n
 * in /usr/src/linux/.config or
 *     Device Drivers --->
 *         USB support  --->
 *             [ ] USB Printer support
 * Alternatively, just disable the usb useflag for cups (your printer
will still work).

 * Error messages for package www-client/seamonkey-bin-2.26.1:

 *
 * Installation of a symlink is blocked by a directory:
 *   '/opt/seamonkey/plugins'
 * This symlink will be merged with a different name:
 *   '/opt/seamonkey/plugins.backup.0017'
 *
 *
 * The following 4 packages have failed to build or install:
 *
 *  (dev-perl/glib-perl-1.301.0::gentoo, ebuild scheduled for merge),
Log file:
 *   '/var/log/portage/dev-perl:glib-perl-1.301.0:20140915-235806.log'
 *  (dev-perl/DBD-mysql-4.20.0-r1::gentoo, ebuild scheduled for merge),
Log file:
 *   '/var/log/portage/dev-perl:DBD-mysql-4.20.0-r1:20140916-001541.log'
 *  (sys-libs/db-4.8.30-r1::gentoo, ebuild scheduled for merge), Log file:
 *   '/var/log/portage/sys-libs:db-4.8.30-r1:20140916-002240.log'
 *  (dev-vcs/subversion-1.8.10::gentoo, ebuild scheduled for merge), Log
file:
 *   '/var/log/portage/dev-vcs:subversion-1.8.10:20140916-012216.log'
 *

!!! existing preserved libs found

emerge @preserved-rebuild

 * IMPORTANT: 2 news items need reading for repository 'gentoo'.
 * Use eselect news to read news items.

Calculating dependencies... done!

emerge: there are no ebuilds to satisfy "dev-lang/python:3.1".

How to remove old "preserved-rebuild"?


-- 
Joseph

Re: [gentoo-user] removing preserve rebuild.

[Joseph]

On 09/15/14 22:29, Joseph wrote:

>emerge @preserved-rebuild
>
> * IMPORTANT: 2 news items need reading for repository 'gentoo'.
> * Use eselect news to read news items.
>
>Calculating dependencies... done!
>
>emerge: there are no ebuilds to satisfy "dev-lang/python:3.1".
>
>How to remove old "preserved-rebuild"?

How do I deal, with the above?

-- 
Joseph

Re: [gentoo-user] removing preserve rebuild.

[Tomas Mozes]

On 2014-09-16 07:23, Joseph wrote:
> On 09/15/14 22:29, Joseph wrote:
> 
>> emerge @preserved-rebuild
>> 
>> * IMPORTANT: 2 news items need reading for repository 'gentoo'.
>> * Use eselect news to read news items.
>> 
>> Calculating dependencies... done!
>> 
>> emerge: there are no ebuilds to satisfy "dev-lang/python:3.1".
>> 
>> How to remove old "preserved-rebuild"?
> 
> How do I deal, with the above?

Upgrade to Python 3.2/3.3, Python 3.1 was removed from portage.

Re: [gentoo-user] removing preserve rebuild.

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 561 bytes --]

On Mon, 15 Sep 2014 23:23:38 -0600, Joseph wrote:

> >emerge @preserved-rebuild
> >
> > * IMPORTANT: 2 news items need reading for repository 'gentoo'.
> > * Use eselect news to read news items.
> >
> >Calculating dependencies... done!
> >
> >emerge: there are no ebuilds to satisfy "dev-lang/python:3.1".
> >
> >How to remove old "preserved-rebuild"?  
> 
> How do I deal, with the above?

Have you read the news items? Are they relevant?


-- 
Neil Bothwick

"I am a Cub Ranger. We dib dib dib for the One. We dob dob dob for the
One."

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

Re: [gentoo-user] removing preserve rebuild.

[Alan McKinnon]

On 16/09/2014 07:23, Joseph wrote:
> On 09/15/14 22:29, Joseph wrote:
> 
>> emerge @preserved-rebuild
>>
>> * IMPORTANT: 2 news items need reading for repository 'gentoo'.
>> * Use eselect news to read news items.
>>
>> Calculating dependencies... done!
>>
>> emerge: there are no ebuilds to satisfy "dev-lang/python:3.1".
>>
>> How to remove old "preserved-rebuild"?
> 
> How do I deal, with the above?
> 

remove python-3.1 from world
update deep newuse world
depclean
emerge @preserved-rebuild


-- 
Alan McKinnon
alan.mckinnon@gmail.com

Re: [gentoo-user] removing preserve rebuild.

[Joseph]

On 09/16/14 14:20, Alan McKinnon wrote:
>On 16/09/2014 07:23, Joseph wrote:
>> On 09/15/14 22:29, Joseph wrote:
>>
>>> emerge @preserved-rebuild
>>>
>>> * IMPORTANT: 2 news items need reading for repository 'gentoo'.
>>> * Use eselect news to read news items.
>>>
>>> Calculating dependencies... done!
>>>
>>> emerge: there are no ebuilds to satisfy "dev-lang/python:3.1".
>>>
>>> How to remove old "preserved-rebuild"?
>>
>> How do I deal, with the above?
>>
>
>remove python-3.1 from world
>update deep newuse world
>depclean
>emerge @preserved-rebuild

Yes, that is what I did solved the problem.
I think I will have to upgrade my system every 2-months not 3-months :-/

-- 
Joseph

Re: [gentoo-user] removing preserve rebuild.

[Alan McKinnon]

On 16/09/2014 15:52, Joseph wrote:
> On 09/16/14 14:20, Alan McKinnon wrote:
>> On 16/09/2014 07:23, Joseph wrote:
>>> On 09/15/14 22:29, Joseph wrote:
>>>
>>>> emerge @preserved-rebuild
>>>>
>>>> * IMPORTANT: 2 news items need reading for repository 'gentoo'.
>>>> * Use eselect news to read news items.
>>>>
>>>> Calculating dependencies... done!
>>>>
>>>> emerge: there are no ebuilds to satisfy "dev-lang/python:3.1".
>>>>
>>>> How to remove old "preserved-rebuild"?
>>>
>>> How do I deal, with the above?
>>>
>>
>> remove python-3.1 from world
>> update deep newuse world
>> depclean
>> emerge @preserved-rebuild
> 
> Yes, that is what I did solved the problem.
> I think I will have to upgrade my system every 2-months not 3-months :-/


No, update the system as often as you like. Going from every 3 months to
every 2 months is not really going to help at all as the same problem
will still be there for both. If you want it quicker than every 3
months, make it every week.

One more thing - please choose a better subject than "gentoo" for your
mails. Thanks.



-- 
Alan McKinnon
alan.mckinnon@gmail.com

[gentoo-user] Re: gentoo

[James]

Joseph <syscon780 <at> gmail.com> writes:

> 
> After recent emerge I get few blockers, that I don't know what to do 
> with it My box has not been updated for 3-months :-/

Joseph,

The problems with  perl updates are not new. It was discussed on this
list quite a bit the last few months. If your update cycle is more than
a few weeks, you are going to miss the relevant discussions on gentoo-user
that solve most of your issues; so maybe update your system weekly_ish?
(and browse gentoo-user).

> emerge: there are no ebuilds to satisfy "dev-lang/python:3.1".

" eselect  python list "

will show your current active version of python. Most all (stable) systems
have a version 2 (2.7) and version 3 (3.3) installed. I'm not
sure why your system did not upgrade 3.1 to 3.3, during the course
of routine upgrades. Also run:

"python-updater" 

after compiling new or removing old version of
python. python is system *critical* so be cautious when performing
install/removal admin tasks on python.



hth,
James

Re: [gentoo-user] Re: gentoo

[Joseph]

On 09/16/14 14:18, James wrote:
>Joseph <syscon780 <at> gmail.com> writes:
>
>>
>> After recent emerge I get few blockers, that I don't know what to do
>> with it My box has not been updated for 3-months :-/
>
>Joseph,
>
>The problems with  perl updates are not new. It was discussed on this
>list quite a bit the last few months. If your update cycle is more than
>a few weeks, you are going to miss the relevant discussions on gentoo-user
>that solve most of your issues; so maybe update your system weekly_ish?
>(and browse gentoo-user).
>
>> emerge: there are no ebuilds to satisfy "dev-lang/python:3.1".
>
>" eselect  python list "
>
>will show your current active version of python. Most all (stable) systems
>have a version 2 (2.7) and version 3 (3.3) installed. I'm not
>sure why your system did not upgrade 3.1 to 3.3, during the course
>of routine upgrades. Also run:
>
>"python-updater"
>
>after compiling new or removing old version of
>python. python is system *critical* so be cautious when performing
>install/removal admin tasks on python.
>
>
>
>hth,
>James

Good suggestion.
Running:
# eselect python list
# eselect python set (put number for python:3.3)
# emerge -C dev-lang/python:3.1
# python updater

solved all the problems.
I was at python:3.3 but for some reason or another (mostly my fault) I did not unmerged python:3.1

When it comes to upgrading be-weekly maybe but from my experience, when I was doing it more often, occasionally, I ended up with a broken system that was caused by new 
packages.
I have 4-boxes at home and two boxes at a remote location.  So the boxes at home get upgraded first, I wait a week, just to make sure every program works and 
then I upgrade one box on a remote location, wait one week again and upgrade the second box (the backup) in the remote location.
So doing it even every second week would be too often for this routine.  
The boxes are "rsync" to one local box.

-- 
Joseph

Re: [gentoo-user] Re: gentoo

[J. Roeleveld]

On 16 September 2014 17:02:43 CEST, Joseph <syscon780@gmail.com> wrote:
>On 09/16/14 14:18, James wrote:
>>Joseph <syscon780 <at> gmail.com> writes:
>>
>>>
>>> After recent emerge I get few blockers, that I don't know what to do
>>> with it My box has not been updated for 3-months :-/
>>
>>Joseph,
>>
>>The problems with  perl updates are not new. It was discussed on this
>>list quite a bit the last few months. If your update cycle is more
>than
>>a few weeks, you are going to miss the relevant discussions on
>gentoo-user
>>that solve most of your issues; so maybe update your system
>weekly_ish?
>>(and browse gentoo-user).
>>
>>> emerge: there are no ebuilds to satisfy "dev-lang/python:3.1".
>>
>>" eselect  python list "
>>
>>will show your current active version of python. Most all (stable)
>systems
>>have a version 2 (2.7) and version 3 (3.3) installed. I'm not
>>sure why your system did not upgrade 3.1 to 3.3, during the course
>>of routine upgrades. Also run:
>>
>>"python-updater"
>>
>>after compiling new or removing old version of
>>python. python is system *critical* so be cautious when performing
>>install/removal admin tasks on python.
>>
>>
>>
>>hth,
>>James
>
>Good suggestion.
>Running:
># eselect python list
># eselect python set (put number for python:3.3)
># emerge -C dev-lang/python:3.1
># python updater
>
>solved all the problems.
>I was at python:3.3 but for some reason or another (mostly my fault) I
>did not unmerged python:3.1
>
>When it comes to upgrading be-weekly maybe but from my experience, when
>I was doing it more often, occasionally, I ended up with a broken
>system that was caused by new 
>packages.
>I have 4-boxes at home and two boxes at a remote location.  So the
>boxes at home get upgraded first, I wait a week, just to make sure
>every program works and 
>then I upgrade one box on a remote location, wait one week again and
>upgrade the second box (the backup) in the remote location.
>So doing it even every second week would be too often for this routine.
> 
>The boxes are "rsync" to one local box.

I am starting to wonder.
How exactly do you upgrade the other machines? 
Copying the entire filesystem?

--
Joost
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: [gentoo-user] Re: gentoo

[Joseph]

On 09/16/14 17:57, J. Roeleveld wrote:
[snip]
>>
>>solved all the problems.
>>I was at python:3.3 but for some reason or another (mostly my fault) I
>>did not unmerged python:3.1
>>
>>When it comes to upgrading be-weekly maybe but from my experience, when
>>I was doing it more often, occasionally, I ended up with a broken
>>system that was caused by new
>>packages.
>>I have 4-boxes at home and two boxes at a remote location.  So the
>>boxes at home get upgraded first, I wait a week, just to make sure
>>every program works and
>>then I upgrade one box on a remote location, wait one week again and
>>upgrade the second box (the backup) in the remote location.
>>So doing it even every second week would be too often for this routine.
>>
>>The boxes are "rsync" to one local box.
>
>I am starting to wonder.
>How exactly do you upgrade the other machines?
>Copying the entire filesystem?

I rsync one local server and all other machine are rsync to it.
My main idea is trying not to introduce to many newer versions packages as in the past I've notice that that could cause the problem.

The is no need for sarcasm. I basically do what works and I do learn from my experience (sometimes :-/).

-- 
Joseph

Re: [gentoo-user] Re: gentoo

[Alan McKinnon]

On 16/09/2014 20:05, Joseph wrote:
> On 09/16/14 17:57, J. Roeleveld wrote:
> [snip]
>>>
>>> solved all the problems.
>>> I was at python:3.3 but for some reason or another (mostly my fault) I
>>> did not unmerged python:3.1
>>>
>>> When it comes to upgrading be-weekly maybe but from my experience, when
>>> I was doing it more often, occasionally, I ended up with a broken
>>> system that was caused by new
>>> packages.
>>> I have 4-boxes at home and two boxes at a remote location.  So the
>>> boxes at home get upgraded first, I wait a week, just to make sure
>>> every program works and
>>> then I upgrade one box on a remote location, wait one week again and
>>> upgrade the second box (the backup) in the remote location.
>>> So doing it even every second week would be too often for this routine.
>>>
>>> The boxes are "rsync" to one local box.
>>
>> I am starting to wonder.
>> How exactly do you upgrade the other machines?
>> Copying the entire filesystem?
> 
> I rsync one local server and all other machine are rsync to it.


*what* do you rsync? Not whihc machine rsyncs to what, he's asking what
files and directories exactly do you rsync?


> My main idea is trying not to introduce to many newer versions packages
> as in the past I've notice that that could cause the problem.
> 
> The is no need for sarcasm. I basically do what works and I do learn
> from my experience (sometimes :-/).
> 


-- 
Alan McKinnon
alan.mckinnon@gmail.com

Re: [gentoo-user] Re: gentoo

[Joseph]

On 09/16/14 21:11, Alan McKinnon wrote:
>On 16/09/2014 20:05, Joseph wrote:
>> On 09/16/14 17:57, J. Roeleveld wrote:
>> [snip]
>>>>
>>>> solved all the problems.
>>>> I was at python:3.3 but for some reason or another (mostly my fault) I
>>>> did not unmerged python:3.1
>>>>
>>>> When it comes to upgrading be-weekly maybe but from my experience, when
>>>> I was doing it more often, occasionally, I ended up with a broken
>>>> system that was caused by new
>>>> packages.
>>>> I have 4-boxes at home and two boxes at a remote location.  So the
>>>> boxes at home get upgraded first, I wait a week, just to make sure
>>>> every program works and
>>>> then I upgrade one box on a remote location, wait one week again and
>>>> upgrade the second box (the backup) in the remote location.
>>>> So doing it even every second week would be too often for this routine.
>>>>
>>>> The boxes are "rsync" to one local box.
>>>
>>> I am starting to wonder.
>>> How exactly do you upgrade the other machines?
>>> Copying the entire filesystem?
>>
>> I rsync one local server and all other machine are rsync to it.
>
>
>*what* do you rsync? Not whihc machine rsyncs to what, he's asking what
>files and directories exactly do you rsync?

I "rsync" only portage, nothing else on the main server.
Other boxes are arsyning to:
SYNC="rsync://10.0.0.103/gentoo-portage"
10.0.0.103 is running "rsyncd"

Upgrade is as usual. 

-- 
Joseph

[gentoo-user] Re: gentoo

[James]

Joseph <syscon780 <at> gmail.com> writes:

> >I am starting to wonder.
> >How exactly do you upgrade the other machines?


> I rsync one local server and all other machine are rsync to it.
> My main idea is trying not to introduce to many newer versions packages 
> as in the past I've notice that that could cause the problem.

 
> The is no need for sarcasm. I basically do what works and I do 
> learn from my experience (sometimes :-/).


Joseph,

Folks that work on precise computer problems are often "raw" with
one another. "Sarcasm" is an ointment that soothes the pain
of running Gentoo. Verbal abuse develops "thick skin" and most
here on Gentoo User have "thick skin", imho.  Devs on this
list often question the gentoo-user base to ferret out if they
need to modify docs, codes or semantics at Gentoo, or if the user
needs. Sometime it does resemble a court room.

 "Alan's school of admin abuse" type of treatment to motivate
an excellent user base is not uncommon.

That said, the amount of questions and bandwidth you have incurred
on this group, does warrant administrative incursion into you
admin policies, imho. Maybe, just maybe, folks actually care
that you are wisely successful with Gentoo?

For example since you are distributing, you really need to keep
binaries packages on at least one system. I nuked python, some
years ago. It was only the files on another similar system that 
prevent me form a new installation of the system.

Besides, I rather think you are being "groomed" to become a gentoo
dev, so you can abuse the rest of of (gentoo users) commoners?


hth,
James

Re: [gentoo-user] Re: gentoo

[Joseph]

On 09/16/14 19:58, James wrote:
[snip]
>
>Folks that work on precise computer problems are often "raw" with
>one another. "Sarcasm" is an ointment that soothes the pain
>of running Gentoo. Verbal abuse develops "thick skin" and most
>here on Gentoo User have "thick skin", imho.  Devs on this
>list often question the gentoo-user base to ferret out if they
>need to modify docs, codes or semantics at Gentoo, or if the user
>needs. Sometime it does resemble a court room.
>
> "Alan's school of admin abuse" type of treatment to motivate
>an excellent user base is not uncommon.
>
>That said, the amount of questions and bandwidth you have incurred
>on this group, does warrant administrative incursion into you
>admin policies, imho. Maybe, just maybe, folks actually care
>that you are wisely successful with Gentoo?
>
>For example since you are distributing, you really need to keep
>binaries packages on at least one system. I nuked python, some
>years ago. It was only the files on another similar system that
>prevent me form a new installation of the system.
>
>Besides, I rather think you are being "groomed" to become a gentoo
>dev, so you can abuse the rest of of (gentoo users) commoners?
>
>
>hth,
>James

Thank for suggestions, yes I usually keep the binaries for as long as I have enough room on "/" :-)
If I'm short on space I periodically nuke them. I've manged to keep the system going for the last 10-years
and keep my own help-file.txt (notes) how to solve certain problem (but not all :-/)

I sometime clean the distribution files with this command (I'm sure there might be a better way).
-----------------
cd /usr/portage/distfiles

and run this command:
(emerge -epf world  2>&1 | perl -ne '$f=join("\n", m@\w://[^\s]+/([^\s]+)@g); print "$f\n" if $f' | sort -u; ls -f) | sort | uniq -c | perl -ane 'print "$F[1]\n" if 
$F[0]==1 && -f $F[1]' | xargs rm -f
------------------

Regarding keeping the binaries, I'll need to learn how to install compiled binaries from another box.  Never, had a chance to do it yet.

-- 
Joseph

Re: [gentoo-user] Re: gentoo

[Alan McKinnon]

On 16/09/2014 22:23, Joseph wrote:
> On 09/16/14 19:58, James wrote:
> [snip]
>>
>> Folks that work on precise computer problems are often "raw" with
>> one another. "Sarcasm" is an ointment that soothes the pain
>> of running Gentoo. Verbal abuse develops "thick skin" and most
>> here on Gentoo User have "thick skin", imho.  Devs on this
>> list often question the gentoo-user base to ferret out if they
>> need to modify docs, codes or semantics at Gentoo, or if the user
>> needs. Sometime it does resemble a court room.
>>
>> "Alan's school of admin abuse" type of treatment to motivate
>> an excellent user base is not uncommon.
>>
>> That said, the amount of questions and bandwidth you have incurred
>> on this group, does warrant administrative incursion into you
>> admin policies, imho. Maybe, just maybe, folks actually care
>> that you are wisely successful with Gentoo?
>>
>> For example since you are distributing, you really need to keep
>> binaries packages on at least one system. I nuked python, some
>> years ago. It was only the files on another similar system that
>> prevent me form a new installation of the system.
>>
>> Besides, I rather think you are being "groomed" to become a gentoo
>> dev, so you can abuse the rest of of (gentoo users) commoners?
>>
>>
>> hth,
>> James
> 
> Thank for suggestions, yes I usually keep the binaries for as long as I
> have enough room on "/" :-)
> If I'm short on space I periodically nuke them. I've manged to keep the
> system going for the last 10-years
> and keep my own help-file.txt (notes) how to solve certain problem (but
> not all :-/)
> 
> I sometime clean the distribution files with this command (I'm sure
> there might be a better way).
> -----------------
> cd /usr/portage/distfiles
> 
> and run this command:
> (emerge -epf world  2>&1 | perl -ne '$f=join("\n",
> m@\w://[^\s]+/([^\s]+)@g); print "$f\n" if $f' | sort -u; ls -f) | sort
> | uniq -c | perl -ane 'print "$F[1]\n" if $F[0]==1 && -f $F[1]' | xargs
> rm -f


eclean (in package gentoolkit)


> ------------------
> 
> Regarding keeping the binaries, I'll need to learn how to install
> compiled binaries from another box.  Never, had a chance to do it yet.

scp/rsync/whatever from one source to $PKGDIR on dest then
emerge -k (or -K depending if you want to fall back to regular compile
from source or not)

or, nfs mount $PKGDIR on the source to $PKGDIR on the dest machine and
you don't have to scp/rysnc


-- 
Alan McKinnon
alan.mckinnon@gmail.com

[gentoo-user] Re: gentoo

[James]

Joseph <syscon780 <at> gmail.com> writes:

> Regarding keeping the binaries, I'll need to learn how to install 
> compiled binaries from another box. 
> Never, had a chance to do it yet.

DIRT simple (general scheme; ymmv).

Look at the working system. Determine where the binaries go, symlinks
etc etc.

"scp" the file(s) over to the damaged box (ip addresss/filepath to ip
address/filepath.

Sometimes you have to do other things (source a file, nuke/reinstate
a symlink etc etc.

That's all I've had to do on similar CPU_arch machines.
I try and keep profiles and use flags similar and put
other use flag in package specific locations.  

scp is my buddy!


hth,
James