Sa Mär 09 13:19:41 2013
Good afternoon
Thank You for help.
> >
> > Yeah, that would be what I consider the bad luck part. My point
was just
> > that relying on a distribution's repositories is not the only option
> > available for installing software in linux - That's what the comment I
> > responded to seemed to be saying. There are often ways around
dependency
> > issues if a program is wanted bad enough - at least that has been my
> > limited experience.
> >
>
> Well my limited experience began in 1996 for Linux. For the first 6
> years I ran Linux I mainly used Slackware too. Back then Slackware
> wasn't known for its strong package management either. It was a great
> system, simple enough anyone could hack around with it, solid enough it
> was predictable out of the box too. But once you started adding to it on
> your own then things quickly got very difficult to keep up with.
>
> By 2001 I'd given that life up for the much easier RPM method of dealing
> with things. That was a golden era then, full of promise, and hope for
> the future. Then Red Hat became a publicly traded company, but that is a
> story for another time ...
>
> Anyhow, be careful what you want, you just may get it, then come to
> realize it isn't worth the trouble after all.
>
> Fact is there is a reason every distribution uses virtually the same
> scheme of package management that keeps track of versions, dependencies,
> and files today. Because no one really wants to do that on their own. It
> is in a word drudgery. It is dull, boring, tedious, and hard too! But
> most of all it is ultimately a waste of time. Duplication of effort
> always is.
*
Is the best way
if the updates does make problems with the os
to download a new iso-file and install Linux again
or is there a cleaning procedure?
Regards
Sophie
Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (20) |
No comments:
Post a Comment