OK, you think you became pragmatic.

My wife get paid for editing video. Before our powermac G5 die she used FinalCut on MacOS X. Now she's using Premier on Windows 7.

If you use kdenlive you have time to lose. Rethink your strategy.

It goes deeper than that, it goes deep into the soul

Yeah, "Bob" appeared to my mother the day I was conceived, and saith unto her: "Blessed art thou, for ye shall bear a son, and he shall be a Slacker from now unto the end of his days."
Praise "Bob"!

1 members found this post helpful.

http://www.studioware.org/packages/s...64-14.1/video/
http://www.studioware.org/slackbuild...ideo/kdenlive/
http://www.studioware.org/

We have package/slackbuild downloaders/installers too.

I can't honestly see how someone so used to slackware would switch to opensuss

Wow, I didn't expect so much in the way of responses to my defecting to Suse as my desktop choice, but to try and answer some of the critics. Yes, I knew what I was getting into when I started using Slackware all those years ago and TBH, back then, it was probably the best distro out there.
But time moves on and while it has been renewed and kept up to date software wise, on a philosophical level, it remains seated firmly in the past. Now that's a good thing where using it to power a server is concerned, hence why I am retaining it for my server. An i5 with (as a recent upgrade) 16Gb ram and a 5 drive raid 5 setup with 1.78Tb of space.

When it comes to the desktop though, I can no longer justify all the crud that goes into getting software packages, whatever they are, installed where it takes so long and is so wasteful of my time. In this day and age of alternatives, I shouldn't be having to read through reams of documentation and finding dependencies when I should be using my time rather more productively than waiting yet again for a build process that may or may not finish successfully.
In effect, I'm fed up after 10 years of being my own desktop admin, it's time to call it a day.
That's not to say that those people here who value and prefer that way of doing things are wrong, just that it has become wrong for me.

So I thank you all for the comments here, even the not very supportive or helpful ones and wish you all the best with your own personal choices. And who knows, maybe one day Pat will embrace one of the thus far unofficial ways of making Slackware a bit easier with one of the community efforts to get dependency resolution included. After all, those people who are attempting this must be doing it for a reason. maybe then I'll come back.

But for now at least, I am happy with my decision. It's early days with Suse so far, but I am liking what I see. And as I retained my original home partition anyway it doesn't look any different.

So good luck to one and all.

Cheers

I understand you now but still don't agree. As many people said before, using sbopkg with sqg is an easy way to get what you want.

So you're delegating the packaging process to someone else, who goes through all the hassles for you. But do you think, that strategy will work in the long-term? The important questions are:

1. Why do we need these middle men packaging 3rd party application software into rpm/deb packages for us?
2. Who pays these middle men for doing that?
3. What happens if they stop providing us with their services?

2 members found this post helpful.

That's what Slackware is in fact - a "distribution". i.e. Someone else builds it for you. The main differences are smaller repos and lack of dependency resolution - still a distro with packaging and still "delegating" to "middlemen".

"Middlemen" also put together slackbuild scripts and check them and host them and provide docs, etc...

If you feel strongly about what you've said - just build up a system from scratch.

3 members found this post helpful.

Yeah, I understand that, and have used sbopkg in the past with assembling build quese, but it's still the time taken to do the build, which is time wasted. As an example, just before I switched, I used sbopkg to install Chromium. It took 3 hrs 17minutes. In Suse, it took slightly less than a minute.

But you know, we could keep this going for ages which is only really rehashing old stuff. My original reason for the post was to say tara. (Hey, it's an old brummy way of saying goodbye) And a thanks to all who have helped me.

I will certainly be popping in and out for any help needed server wise, though I seem to have that down to a fine art. For now though:

Adios
Au Revoir
Tschus
Arrivederci
Dosvedanya
Cheers

Everybody is entitled to change their mind about anything at any time, and shouldn't have to explain their actions at any length to anyone else.
Don't forget to keep that 10p set aside, vdemuth, just in case.

2 members found this post helpful.

Oh I see, here things usually don't take that long to compile. Anyways, when I need a binary I search into Alien's repository.

Slackware is a commercial operating system. Providing packages for every existing application is out of its scope. I'm glad that people exist, who create Slackbuilds and packages voluntarily. But what is wrong with the ecosystem, if we need such an immense effort in the first place just for installing applications like Kdenlive?

@vdemuth

Well, I'm sad to hear that, but you've made a carefully considered decision about what's best for you. So go for it.