Refreshing the source in yast2 sw_single should be skippable
Say, if I want to install a single package that I know it's on the media, I have to wait for yast2 to complete refreshing all the installation sources that I have defined. And some of them are large and are on the internet. There isn't any way to skip the refreshing just once, this time. Consequently, a task that should take 1 minute takes 10. Not optimal. If yast2 sw_single + YOU is going to be replaced soon with something from the grander vision, very well, then it's not justified spending resources on this. Else, some buttons or CLI options that will skip the refresh wouldn't hurt.
Silviu Marin-Caea ha scritto:
If yast2 sw_single + YOU is going to be replaced soon with something from the grander vision, very well, then it's not justified spending resources on this. Else, some buttons or CLI options that will skip the refresh wouldn't hurt.
Uhm, I personally think that this is personal taste .... I mean, on the yum-side of the world this is strictly necessary (haven't found - or searched, for what matters - any different option on this) and they have worked out on speeding out yum (using sql-lite IIRC) and the speed of the repos. Now, having slow answering yast repos (sorry pal, but anyone I know here in Italy sais the same and I have a "formal" 4megabits line) are annoying (if not other things). So, *you* have to decide whenever go with a "stable" repo list for a day, a week, a month or to update the list on a regular basis .... it depends on your user profile ... you are running a development machine, a mission critical one, a bleeding-edge laptop ... Cheers, nicola -- .~. Nicola -=KOOLINUS=- Losito /v\ http://www.koolinus.net | http://kool-solutions.blogspot.com // \\ /( )\ Linux Registered User #293182 ^^ ^^ icq:62837984 * Jabber-ID:koolinus@jabber.linux.it
On Thu, 2006-02-02 at 13:39 +0200, Silviu Marin-Caea wrote:
Say, if I want to install a single package that I know it's on the media, I have to wait for yast2 to complete refreshing all the installation sources that I have defined. And some of them are large and are on the internet.
There isn't any way to skip the refreshing just once, this time.
Consequently, a task that should take 1 minute takes 10. Not optimal.
If yast2 sw_single + YOU is going to be replaced soon with something from the grander vision, very well, then it's not justified spending resources on this. Else, some buttons or CLI options that will skip the refresh wouldn't hurt.
Have you tried using yast2 -i some_software_package to install instead? -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
On 02/02/2006 01:30 PM Kenneth Schneider wrote:
Have you tried using yast2 -i some_software_package to install instead?
I am not sure, but was "yast -i" not the one installing with "rpm --nodeps", if you use it with an rpm? Or with a packagename? OJ -- make bzImage, not war.
On Thu, 2006-02-02 at 19:35 +0100, Johannes Kastl wrote:
On 02/02/2006 01:30 PM Kenneth Schneider wrote:
Have you tried using yast2 -i some_software_package to install instead?
I am not sure, but was "yast -i" not the one installing with "rpm --nodeps", if you use it with an rpm? Or with a packagename?
OJ
No. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
On 2/2/2006 8:16 PM Kenneth Schneider wrote:
On Thu, 2006-02-02 at 19:35 +0100, Johannes Kastl wrote:
I am not sure, but was "yast -i" not the one installing with "rpm --nodeps", if you use it with an rpm? Or with a packagename?
No.
Which one? From what I googled now, "yast -i xyz.rpm" is working with "--nodeps --force", so it is ok to use it with the package name. OJ -- Insane people throw computers out of windows, sane people...
Hi, On Thursday, February 02, 2006 at 19:35:17, Johannes Kastl wrote:
On 02/02/2006 01:30 PM Kenneth Schneider wrote:
Have you tried using yast2 -i some_software_package to install instead?
I am not sure, but was "yast -i" not the one installing with "rpm --nodeps", if you use it with an rpm? Or with a packagename?
yast -i is not always the same as yast -i ;) yast -i foo Calls the yast packagemanager and installs the package with the name foo from the known installation sources. Including dependencies. yast -i foo.rpm just calls rpm with nodeps on the file foo.rpm. Henne -- Henne Vogelsang, http://hennevogel.de "To die. In the rain. Alone." Ernest Hemingway
On 2/2/2006 11:36 PM Henne Vogelsang wrote:
yast -i foo.rpm
just calls rpm with nodeps on the file foo.rpm.
Just as I said in my other reply to Kenneth, which I dont see here cos I dont get it over googlemail ;-( OJ -- When you say "I wrote a program that crashed Windows", people just stare at you blankly and say "Hey, I got those with the system, *for free*". (Linus Torvalds)
On Thu, 2 Feb 2006, Silviu Marin-Caea wrote:
Say, if I want to install a single package that I know it's on the media, I have to wait for yast2 to complete refreshing all the installation sources that I have defined. And some of them are large and are on the internet.
There isn't any way to skip the refreshing just once, this time.
Consequently, a task that should take 1 minute takes 10. Not optimal.
If yast2 sw_single + YOU is going to be replaced soon with something from the grander vision, very well, then it's not justified spending resources on this. Else, some buttons or CLI options that will skip the refresh wouldn't hurt.
It's possible to enable/disable autorefresh for an installation source in the "Installation Sources" module or in y2pmsh. If you are using a CD/DVD inst source, it shouldn't do autorefreshing by default. # y2pmsh [...] [0] y2pm > source -ls Known sources: 0: [x] SUSE LINUX Version 10.0.42 (...) [autorefresh] [0] y2pm > source --help Usage: source OPTIONS OPTIONS: -e ID, --enable ID enable source number ID -d ID, --disable ID disable source number ID -a URL, --add URL add a new source at URL -u ID, --update ID updated cached data for ID -R ID, --remove ID remove source number ID -P ID, --product ID install source number ID as product -A ID, --autorefresh ID enable autorefresh on source number ID --noautorefresh ID disable autorefresh on source number ID -s, --show show known sources [0] y2pm > source --noautorefresh 0 [0] y2pm > source -ls Known sources: 0: [x] SUSE LINUX Version 10.0.42 (...) [0] y2pm > # Anyway -- with the upcoming changes in the Package Manager this procedure might fail to work in the future ;( Regards Christoph
participants (6)
-
Christoph Thiel -
Henne Vogelsang -
Johannes Kastl -
Kenneth Schneider -
Nicola -kOoLiNuS- Losito -
Silviu Marin-Caea