Linked by David Adams on Tue 20th Jul 2010 18:07 UTC, submitted by sjvn
SuSE, openSUSE Long time fans of openSUSE Linux and its commercial big brother, Novell's SUSE Linux Enterprise Desktop, will find a lot to like in this latest update.
Thread beginning with comment 434253
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: zypper
by sorpigal on Wed 21st Jul 2010 19:48 UTC in reply to "RE[4]: zypper"
sorpigal
Member since:
2005-11-02

If you get the error you have the deb already. It will be in /var/cache/apt/archives/packagename_version_arch.deb, so you can normally just say dpkg -i --force-depends /var/cache/apt/archives/packagename*deb since you are not likely to have more than one version (especially if you auto prune).

I agree that the breakage of --download-only makes no sense from a user perspective.

That's news to me. Aptitude is a much heavier tool (with a curses ui, even).

I always find this funny, since I have never used the aptitude UI. IMO aptitude is primarily command line and the curses part is just so it can serve as a replacement for people who like dselect, too. For most basic operations the command line syntax is the same: aptitude install foo, aptitude remove foo, aptitude update, etc.. The major differences are in the switches and various options.

It is a bit heavier but I think only on an embedded system would you need to worry about that. I can understand they maemo went with apt-get especially since at the moment the more-correct behavior of aptitude is not very noticable in the real world today.

Reply Parent Score: 2

RE[6]: zypper
by vivainio on Thu 22nd Jul 2010 05:19 in reply to "RE[5]: zypper"
vivainio Member since:
2008-12-26

If you get the error you have the deb already. It will be in /var/cache/apt/archives/packagename_version_arch.deb, so you can normally just say dpkg -i --force-depends /var/cache/apt/archives/packagename*deb since you are not likely to have more than one version (especially if you auto prune).


If the dependencies are failing, the package isn't downloaded to cache at all. Only errors in the packages themselves are solved by this approach.

Reply Parent Score: 2