Mailinglist Archive: opensuse-factory (723 mails)
| < Previous | Next > |
Re: [opensuse-factory] Re: [opensuse-announce] SUSE Linux 10.1 Beta6 is ready
- From: "Ulrich Windl" <ulrich.windl@xxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 03 Mar 2006 11:04:13 +0100
- Message-id: <440822B2.14648.154EA851@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
On 3 Mar 2006 at 9:30, Andreas Jaeger wrote:
> Peter Czanik <pczanik@xxxxxxxxxxxxxx> writes:
[...]
> > In this case, how can I use the factory tree, if I installed from the CD?
> > cd /mnt/factory/inst-source/suse/ppc/
> > rpm -Fvh yast* z* libzypp*
> > and I have a package manager working with factory? Bye,
>
> Yes, correct!
This brings up one question: I have forces an update from SL 9.0 to 9.2 that way,
and everything is fine, only YOU still looks for Updates to 9.0...
Now the question is: How is YaST's product database properly updated to the new
release?
Finally a performance remark: It seems when trying an update to many packages
(like "*.rpm"), rpm is much slower (needs a lot of RAM?) as compared to something
like "echo *.rpm |xargs -n 10 rpm ....". Yes, I know there's a semantic
difference, so you could try reordering the input list until every package is in.
Maybe you can have the same effect with --nodeps...
Regards,
Ulrich
> Peter Czanik <pczanik@xxxxxxxxxxxxxx> writes:
[...]
> > In this case, how can I use the factory tree, if I installed from the CD?
> > cd /mnt/factory/inst-source/suse/ppc/
> > rpm -Fvh yast* z* libzypp*
> > and I have a package manager working with factory? Bye,
>
> Yes, correct!
This brings up one question: I have forces an update from SL 9.0 to 9.2 that way,
and everything is fine, only YOU still looks for Updates to 9.0...
Now the question is: How is YaST's product database properly updated to the new
release?
Finally a performance remark: It seems when trying an update to many packages
(like "*.rpm"), rpm is much slower (needs a lot of RAM?) as compared to something
like "echo *.rpm |xargs -n 10 rpm ....". Yes, I know there's a semantic
difference, so you could try reordering the input list until every package is in.
Maybe you can have the same effect with --nodeps...
Regards,
Ulrich
| < Previous | Next > |