Notices


Reply
Thread Tools
GeneralAntilles's Avatar
Posts: 5,478 | Thanked: 5,222 times | Joined on Jan 2006 @ St. Petersburg, FL
#11
Originally Posted by neatojones View Post
I'm not sure that this is easier. I was already removing other packages for programs I don't use in the default setup. Removing them saved space (not much, but some) for programs I do use. Most users who've figured out the utility of apt-get aren't going to run into problems with this. A newbie, maybe...but I doubt that they're gonna be using the command line for anything. Heck, most have no idea what it is.
You wont save space removing KB-sized installers. Some people wont know apt and those people will be in a jam when they do miss an update. You don't know newbies if you think they wont get themselves into trouble following the recommendation off some random website without knowing what they're getting into.

Originally Posted by neatojones View Post
You'd still get updates. You just won't get that package updated because it's not on your system anymore. The packages that it depended on that you still have installed should still be detected and then updated as well. I've never run into a debian system that worked otherwise (and I used them for years).
Except if a new package is added, a package removed, or renamed. Which was what happened between 23-14 and 30-2. The result was reboot loops for people who had removed osv.

Originally Posted by neatojones View Post
Keeping a repository like this enabled is the problem. Not a dist-upgrade. It should only be enabled for a specific application install (if used at all).
Obviously, but people rarely follow good advice.

Originally Posted by neatojones View Post
Besides, I'd expect that people using this repository would know how to prevent this problem.
See, but that's just it. A simple user-targeted application like Fring adds it, so you can't expect everybody to understand the danger involved, or ever be aware of it.

Originally Posted by neatojones View Post
I've yet to break my device with this command. Anyways, most of the programs that do this are going to uninstall this osso-software-version anyway (as in the case of this user).
You may not have, but there's a very easy way to do it, and there are lots of people who have brought on reboot loops by doing it. Don't expect that everybody has your skills or your own good sense. Most people don't.

Originally Posted by neatojones View Post
While I understand you point of view, I still think my recommendations are quite valid.
Because, I think, you're failing to grasp exactly what sort of creatures users really are (Hint: it's usually neither well-informed nor particularly careful).

On a case-by-case basis, sure, there's nothing wrong with your recommendation. Assuming, of course, that with each case you're sure the person you're making the recommendation to is aware of the risks and repercussions involved, but as a general recommendation it's very dangerous. I'm not inclined to let it past when the end result is going to be more work for me helping people fix the mess that an careless recommendation causes.

So, please, avoid making dangerous general recommendations unless you're willing to step up and provide direct help to everybody that's harmed by them.
__________________
Ryan Abel
 
Posts: 253 | Thanked: 104 times | Joined on Aug 2008 @ Midwest, USA
#12
Since I don't mind helping and am more than willing to help others troubleshoot their broken systems we'll let this discussion serve as fair warning to anyone who follows that advice. Any advice on this website could be dangerous if missused.

I think the real answer is to ask fring to change their policy. These repositories would be available for any upgrade or application install which has dependencies which are included in this repository.

Reread my post and you'll see that I warned about the fact hat new packages might not get installed. Note that I mentioned the drawbacks to removing metapackages such as this one in the original post including the fact that new software might need to be manually installed. Truthfully, packages that would break the system should have dependencies outside of this metapackage (as it's really just a fail safe when used properly) that would cause them to add any new essential packages. So, this is as much of a developer issue as it is a user one, if not truthfully moreso. Aside from mistakes, oversights, and poor judgement by the development team and programmers, I assure you that dist-upgrading to a stable version from a prior stable version should be harmless and no user should be held responsible for any such problem.
 
GeneralAntilles's Avatar
Posts: 5,478 | Thanked: 5,222 times | Joined on Jan 2006 @ St. Petersburg, FL
#13
Originally Posted by neatojones View Post
I think the real answer is to ask fring to change their policy. These repositories would be available for any upgrade or application install which has dependencies which are included in this repository.
I've tried, several times, with no response.
__________________
Ryan Abel
 

The Following User Says Thank You to GeneralAntilles For This Useful Post:
bongo's Avatar
Posts: 291 | Thanked: 124 times | Joined on Feb 2006 @ Trier, Germany
#14
What is the unlocked version for?
__________________
ongo bongo!
 
GeneralAntilles's Avatar
Posts: 5,478 | Thanked: 5,222 times | Joined on Jan 2006 @ St. Petersburg, FL
#15
Originally Posted by bongo View Post
What is the unlocked version for?
http://wiki.maemo.org/Seamless_Software_Update#Unlocked
__________________
Ryan Abel
 
Posts: 160 | Thanked: 85 times | Joined on Jan 2009 @ Greece-Athens
#16
ok. i 've uninstalled that. how can i get it back without reflashing??
 
Posts: 1,208 | Thanked: 1,028 times | Joined on Oct 2007
#17
Originally Posted by GeneralAntilles View Post
Please, dear god, don't do that. An apt-get dist-upgrade with the SDK repository (which is added by several .installs, including the one for Fring) equals an unbootable tablet.

Actually Fring .install hasn't included sdk repository for a long time (at least 2 months).

http://www.fring.com/linux/N810.install
 
Benson's Avatar
Posts: 4,930 | Thanked: 2,272 times | Joined on Oct 2007
#18
Originally Posted by mikkov View Post
Actually Fring .install hasn't included sdk repository for a long time (at least 2 months).

http://www.fring.com/linux/N810.install
Sure, but there's a risk that anyone who installed it before then still has the SDK repo enabled, waiting to blow up in their face.
 

The Following User Says Thank You to Benson For This Useful Post:
Reply


 
Forum Jump


All times are GMT. The time now is 11:57.