[opensuse-factory] Installation source handling in 10.3

older
[opensuse-factory] 45 minutes for...

Marcel Hilzinger

24 Nov 2006 24 Nov '06

13:17

Just a proposal for 10.3, as for 10.2 it's too late anyway: I think the installation source module should not fetch any other data then the source name. It should just put the right info on the right place, like editing /etc/apt/sources.list or a file in /etc/yum/yum.d.repos/ Why? With the current solution, each time you launch the installation source module metadata is fetched. Most of us probably never need this metadata to add a new source. I even doubt, that the module itsef needs this data. If you start the Package Manager after the installation source module, the same data is fetched again. So Suse does 2x the work, which would be needed actually to perform an installation from a new source. -- Mit freundlichen Grüßen, Marcel Hilzinger Linux New Media AG Süskindstr. 4 D-81929 München Tel: +49 (89) 99 34 11 0 Fax: +49 (89) 99 34 11 99 --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

Show replies by date

Adrian Schröter

24 Nov 24 Nov

13:16

Am Friday 24 November 2006 14:17 schrieb Marcel Hilzinger:

...

Just a proposal for 10.3, as for 10.2 it's too late anyway:

I think the installation source module should not fetch any other data then the source name. It should just put the right info on the right place, like editing /etc/apt/sources.list or a file in /etc/yum/yum.d.repos/

Why? With the current solution, each time you launch the installation source module metadata is fetched. Most of us probably never need this metadata to add a new source. I even doubt, that the module itsef needs this data.

if the source is marked as not changing source, this happens only once.

...

If you start the Package Manager after the installation source module, the same data is fetched again. So Suse does 2x the work, which would be needed actually to perform an installation from a new source.

-- Adrian Schroeter SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

Klaus Kaempf

13:17

* Marcel Hilzinger [Nov 24. 2006 14:13]:

...

Just a proposal for 10.3, as for 10.2 it's too late anyway:

I think the installation source module should not fetch any other data then the source name. It should just put the right info on the right place, like editing /etc/apt/sources.list or a file in /etc/yum/yum.d.repos/

When adding a repository, retrieving the metadata is the right thing to do to detect problems. If you start to download metadata when starting a package manager, errors will be quite confusing.

...

Why? With the current solution, each time you launch the installation source module metadata is fetched.

This is wrong and we want to fix this for 10.3. Downloading (resp. refreshing) repository metadata should not be done when starting a software managment application. Klaus --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

Marcel Hilzinger

16:14

Am Freitag, 24. November 2006 14:17 schrieb Klaus Kaempf:

...

* Marcel Hilzinger [Nov 24. 2006 14:13]:

...
Just a proposal for 10.3, as for 10.2 it's too late anyway:

I think the installation source module should not fetch any other data then the source name. It should just put the right info on the right place, like editing /etc/apt/sources.list or a file in /etc/yum/yum.d.repos/

When adding a repository, retrieving the metadata is the right thing to do to detect problems. If you start to download metadata when starting a package manager, errors will be quite confusing.

But why 90% of all package managers work the other way? With apt, smart, yum adding a source needs no internet connection and it's a matter of a second. Metadata is only loaded, when you want to install something. I don't see, why the YaST solution would be better, but feel free to convince me ;-)

...

...
Why? With the current solution, each time you launch the installation source module metadata is fetched.

This is wrong and we want to fix this for 10.3. Downloading (resp. refreshing) repository metadata should not be done when starting a software managment application.

-- Mit freundlichen Grüßen, Marcel Hilzinger Linux New Media AG Süskindstr. 4 D-81929 München Tel: +49 (89) 99 34 11 0 Fax: +49 (89) 99 34 11 99 --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

Klaus Kaempf

16:43

* Marcel Hilzinger [Nov 24. 2006 17:10]:

...

But why 90% of all package managers work the other way? With apt, smart, yum adding a source needs no internet connection and it's a matter of a second. Metadata is only loaded, when you want to install something. I don't see, why the YaST solution would be better, but feel free to convince me ;-)

I just think that getting a 'repository not available' error (due to mistyped URL, server down, whatever) is more intuitive during the actual adding of the repo. There are no technical reasons for one way or the other. Klaus --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

Robby (M9.)

25 Nov 25 Nov

16:20

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Klaus Kaempf schreef:

...

* Marcel Hilzinger [Nov 24. 2006 14:13]:

...
Just a proposal for 10.3, as for 10.2 it's too late anyway:

I think the installation source module should not fetch any other data then the source name. It should just put the right info on the right place, like editing /etc/apt/sources.list or a file in /etc/yum/yum.d.repos/

When adding a repository, retrieving the metadata is the right thing to do to detect problems. If you start to download metadata when starting a package manager, errors will be quite confusing.

...
Why? With the current solution, each time you launch the installation source module metadata is fetched.

This is wrong and we want to fix this for 10.3. Downloading (resp. refreshing) repository metadata should not be done when starting a software managment application.

Very well said..!

...

Klaus --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFFaG1pX5/X5X6LpDgRAi9lAJ9wi5B+rpGidsVuG72VucpAxwgfSACgxFt5 ho01Y/vpQq+iXks1yku7JqA= =CRsE -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

Robby (M9.)

16:18

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Marcel Hilzinger schreef:

...

Just a proposal for 10.3, as for 10.2 it's too late anyway:

I think the installation source module should not fetch any other data then the source name. It should just put the right info on the right place, like editing /etc/apt/sources.list or a file in /etc/yum/yum.d.repos/

I agree, to me it is the most annoying thing in the whole distro: to have to wait half an hour for the meta-data to get downloaded. Now it takes a little shorter, but still much too long. Allmost as annoying as to have to wait for the 'zen-synchronisation'..

...

Why? With the current solution, each time you launch the installation source module metadata is fetched. Most of us probably never need this metadata to add a new source. I even doubt, that the module itsef needs this data.

If you start the Package Manager after the installation source module, the same data is fetched again. So Suse does 2x the work, which would be needed actually to perform an installation from a new source.

-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFFaGztX5/X5X6LpDgRAjg8AJ9LJNkz6VFCDUnzt8aioKmJHIRsVQCeIXCS WTNAEyPWRZc4duwaWAkQiVE= =lELd -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

6368

Age (days ago)

6369

Last active (days ago)

List overview

Download

6 comments

4 participants

participants (4)

Adrian Schröter
Klaus Kaempf
Marcel Hilzinger
Robby (M9.)