Linuxpackages dying?

Daedra · 06-28-2009, 11:26 PM

Quote:

Originally Posted by akiku

I suppose I will the contrarian on this thread and go on record that, in my experience, linuxpackages.net does fill a need that slackbuilds.org cannot: providing a repository of compiled packages for large applications, particularly ones with *lots* of dependencies.

I use mostly old hw or a wimpy netbook with little storage, memory and cpu power, so I try to avoid compiling the big stuff. And I've never experienced the quality issues so many pointed out here.

I have nothing against linuxpackages.net but if you want a repository that has already compiled packages you should check out slacky.eu. This place has always taken a back seat to slackbuilds.org but the work they do over there is quality and they supply buildscripts. http://repository.slacky.eu/slackware-12.2/

Linux.tar.gz · 06-29-2009, 03:38 AM

I used a lot of linuxpackage's .tgz.
"It was" a nice place to begin with, and i never had a problem with the packages i installed.
And i discovered many apps.

kc3 · 06-29-2009, 08:12 AM

Quote:

Originally Posted by SqdnGuns

He is referring to LinuxPackages.........

No I actually do mean Slackbuilds and honestly I can't even remember what was wrong lol, I used their packages a while back and a couple of'm I used wouldn't work, but as I mentioned, compiling from source worked just fine so I'm not worried about it

I could probably try again and get it working but idk, I don't really care enough

pwc101 · 06-29-2009, 08:18 AM

Quote:

Originally Posted by kc3

No I actually do mean Slackbuilds and honestly I can't even remember lol, I used their packages a while back and a couple of'm I used wouldn't work, but as I mentioned, compiling from source worked just fine so I'm not worried about it

SlackBuilds.org doesn't provide precompiled packages, only SlackBuild scripts (hence the name...), so there must be some confusion here.

Back OT...

When I first started using Slack, I installed the odd precompiled package from linuxpackages.net and the slacky.eu repository. Then I used to roll my own and install them using checkinstall. After that it was the turn of src2pkg, but since SlackBuilds.org has kicked off, I've used SlackBuild scripts exclusively ever since, be they ones from SlackBuilds.org, Alien's repository, Robby's repository, slacky.eu's repository or some random site on the net with a SlackBuild. When the latter is the case, I tend to hack out all the bits I'm not comfortable with (the odd fakeroot, for instance) and use that.

Otherwise, I write my own and submit them to SlackBuilds.org, and reference other scripts when I've taken my queue from them.

But precompiled packages were definitely useful to me at first - things might have turned out differently if they'd not been around, and I might still be a Fedora user. It's a funny old world.

hitest · 06-29-2009, 08:22 AM

Quote:

Originally Posted by kc3

No I actually do mean Slackbuilds and honestly I can't even remember what was wrong lol, I used their packages a while back and a couple of'm I used wouldn't work, but as I mentioned, compiling from source worked just fine so I'm not worried about it

I could probably try again and get it working but idk, I don't really care enough

Sounds like a PEBKAC issue to me. Slackbuilds work perfectly if you read and use the tutorial provided at slackbuilds.org.
Building from source is just fine, but, I prefer the slackbuild way.
Each to his own though.

Cotobear · 08-31-2009, 09:43 PM

Sorry to resurrect this thread.

It seems the lights are still flickering at linuxpackages.net. A new post was made about Slackware 13.0 on the main page.