Hi,
I have the impression that when rsync'ing /usr/portage/packages from
another machine (BINSERVER),
emerge --update --newuse --deep --buildpkg @system @world
doesn't update packages which are upto-date on BINSERVER
but not upto-date on the local machine.
What's the role of the file
Am Dienstag, 15. September 2009 schrieb Helmut Jarausch:
Hi,
I have the impression that when rsync'ing /usr/portage/packages from
another machine (BINSERVER),
emerge --update --newuse --deep --buildpkg @system @world
doesn't update packages which are upto-date on BINSERVER
but not upto-date
On Tue, 15 Sep 2009 15:21:50 +0200
Frank Steinmetzger wrote:
Here it stores alotta info about the binary packages - for instance
with what useflags they were compiled. This info is not in the
archives, which only contain the files.
No, informations about environment are included in tbz2
On Tue, 15 Sep 2009 15:19:01 +0200 (CEST), Helmut Jarausch wrote:
I have the impression that when rsync'ing /usr/portage/packages from
another machine (BINSERVER),
emerge --update --newuse --deep --buildpkg @system @world
doesn't update packages which are upto-date on BINSERVER
but not
On 15 Sep, Neil Bothwick wrote:
On Tue, 15 Sep 2009 15:19:01 +0200 (CEST), Helmut Jarausch wrote:
I have the impression that when rsync'ing /usr/portage/packages from
another machine (BINSERVER),
emerge --update --newuse --deep --buildpkg @system @world
doesn't update packages which are
On Tuesday 15 September 2009 15:04:23 Fabrice Delliaux wrote:
On Tue, 15 Sep 2009 15:21:50 +0200 Frank Steinmetzger wrote:
Here it stores alotta info about the binary packages - for instance
with what useflags they were compiled. This info is not in the
archives, which only contain the
6 matches
Mail list logo
