I don't know. Post @ppr:kut is interesting. It provided some arguments: what is required and task complexity. For me most interesting is that Slackware packages are "too big". What does it mean?

Edit: People referring to Salix should understand that Salix is on top of stable release. Now Salix is stuck at 14.2. Besides Salix is using its own binaries repository and app called Sourcery for slackbuilds - to automate build from salckbuilds scripts.

This reply is to everyone but 'gerogerigegege':

When I see posts like this one I just ignore them and don't get involved... not this time though, it's a slow day...

I notice there are two types of people on LQ: those like me that can usually 'ignore' and those that take such posts as earnest queries and so they reply in good faith.

I also notice that people like 'gerogerigegege' (wow did I spell that right?)
usually put out one polemical post then sit back quiet like and never reply. So far this post has generated 5 pages of posts, but only the first one is from gero...etc.

I think everyone is missing the point here. Slackware has had dependency checking from day-one, otherwise nothing would work, and as a user I'm very happy with it. I've no complaints. Keep up the great work Pat, and thank you.

On the one hand you are correct, on the other hand if the thread is quickly derailed from the OP's intentions - I see it as a win .

@Jeebiz

You're correct - I now have to update my little rule...there 3 types of people on LQ: the ignorers, the believers, and the derailers!

How do I join the derailers? :-)

You have already joined , now just bring up something that is not related to the OP's thread

And with that I think you just won the Internet for me today!

Thanks for the chuckle, hazel!


Thanks
--
KarlMag

Actually, he has made three posts in this thread.

@Jeebizz

I not sure if I agree with your statement "The keystroke is mightier than the mouseclick". Have you tried typing a document with a joystick? Its the way of the future man.

I guess this is why the question of shutdown- and bootup speeds actually comes up (aka reboots).
One typically wants one's systems down for as short of a time as possible.

Of course some may have more legitimate reasons for wanting that than others - How many nines percentage have you committed your uptime to be?



Thanks
--
KarlMag

Not at all my friend. Just saying that there is room for different things here. If you don't like Slackware the way it is, I'm ok with that. There are plenty of us who do, so why should it change? There are plenty of other distributions which can scratch your itch. They don't all need to be the same.

Thanks for asking about my day. It went quite well. It was very productive.

2 members found this post helpful.

Agreed! I love and use Slackware and a lot of other operating systems. I'm a curious person.

Let me speak from experience. I maintain Slint, one of the Slackware derivatives. Dependencies are handled te same way by Salix, Slackel and Slint. As an aside, dependencies of Slackware packages is available here: http://slackware.uk/salix/x86_64/slackware-14.2/deps provided by George Vlahavas aka gapan, Salix maintainer.

But to compete with other distributions, the main issue (common to Slackware and all its derivatives) is rather that we provide a lot less software in the repositories of each distribution. I won't speak for others, but in Slint cases this is because being the only one to do the packaging, I can't maintain as many software as distributions that have dozens if not hundreds of packagers. And indeed using third party repositories has its limitations, the main one being that their packages are not guaranteed to be built in the same context, or at compatible versions.

Indeed there's SBo, but many users prefer to get pre-built packages, even considering the various tools that make building and installing packages from what SBo provides relatively easy in most cases. And also appreciate that the overall set of provided packages be modular, so that to give just an example they can just pick the desktop they want among many proposed.

1 members found this post helpful.

I'll take your word for it. I now have to update my little rule...there 4 types of people on LQ: the ignorers, the believers, the derailers, and the counters!

Well I keep hearing how touchscreen is the future - but I seriously doubt coders will throw away their keyboards, and code on a touchscreen .

1 members found this post helpful.