SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
And remember, there is only going to be Slackware as long as Pat Volkerding and family can make a living out of it. the sales of CD's and DVD's is about their only income (and it has to be shared with the people running the Slackware Store), and I can tell you, it is not a pot of gold at all.
Buy the disks, people! I'd like to help program the OS but it's too hard.
Buy the disks, people! I'd like to help program the OS but it's too hard.
Lucky for you... there is no programming involved in maintaining the Slackware OS - at least not for the Slackware team.
Unless you consider shell scripting as programming.
Once I wrote a script that output text to the screen in different colors and made the computer go "BEEP". But if the future of Slackware depends on me becoming a contributor then the project might be doomed.
Ok, but Alien's packages aren't official and supported by Slackware team.
I'm also havily using alien's repository, so I don't skip them in my daily work - no. I was skipping them in previous post, because they aren't official!
So what do you have to say about Slackware 13.1 X86_64?
How do you think that evolved? Eric's direct interaction & as a member of the Slackware team does contribute to Slackware. He does keep his packages separate from SlackBuilds. How do you think Slackware gets some of it's packages? Eric's KDE work, X86_64, and even scripting for initialization scripts for Slackware to just name a few. I'll let Alien_Bob defend his position but I have been using Slackware since the first days.
So what do you have to say about Slackware 13.1 X86_64?
How do you think that evolved? Eric's direct interaction & as a member of the Slackware team does contribute to Slackware. He does keep his packages separate from SlackBuilds. How do you think Slackware gets some of it's packages? Eric's KDE work, X86_64, and even scripting for initialization scripts for Slackware to just name a few. I'll let Alien_Bob defend his position but I have been using Slackware since the first days.
eh? I didn't see Eric's position attacked such that it needs defending!
The officialness of the thing being provided has no bearing on the standing of the person providing it. Pat himself could bring out some 'unofficial' patches if he really wanted to.
All I saw was that Martinezio said that Eric's KDE builds were unofficial - a statement which I'm sure Eric himself would agree with. Just like his multilib is "unofficial".
Oh. bu I did not feel attacked at all by calling my packages "unofficial"... because that's what they are. They are not supported by the Slackware Team as a whole, only by me (even if I am a part of that team).
My "ktown" KDE packages are as close to being "official" as possible because I use the Slackware build scripts and ultimately, the versions of KDE that I build and you test end up in Slackware anyway.
Slightly OT, maybe, but regarding "unofficial" vs. "official" packages: SlackBuilds.org packages are "nearly official". Some of them become "official" in a later release of Slackware.
One package I definitely would like to see already in Slackware 13.2 is fdupes.
I've tried many tools to identify duplicate files on my disks, but fdupes is by far the fastest.
I personnaly find KDE totally inefficient. A paradigm of what one does not want a desktop to be.
Does anybody know if there are plans to release a KDE light? This would probably be welcome by a lot of users.
Meanwhile I am quite satisfied with Xfce4 --driving the KDE applications of course! (K3B, Amarok, Ktorrent, and all the goodies...)
Official shmaficcial... I am just incredibly thankful to Alien dude for delivering behemoths like LibreOffice (x64, bandwidth included!) in a timely and painless manner that should make Ubuntu users jealous (what with their unofficial repositories and mysterious spell checker dependencies). Once again, an amazing job.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,094
Rep:
Quote:
Originally Posted by qweasd
Official shmaficcial... I am just incredibly thankful to Alien dude for delivering behemoths like LibreOffice (x64, bandwidth included!) in a timely and painless manner that should make Ubuntu users jealous (what with their unofficial repositories and mysterious spell checker dependencies). Once again, an amazing job.
Alien Bob is legend as far as I am concerned. I've been using Slackware since 7.1 and it has gotten a whole lot easier to use but still rock sold stable thanks to Alien Bob's scripts.
Because I finally upgraded to 13.1. I always procrastinate and when I finally get around to it the next release comes within a month.
Since it's today the 27'th of January,. and thus exactly one month later... you loose
PS: I to am in doubt what to do. I've got 2 boxes, 13.0 and 13.1, both need some attention (virtual box, and I thought of a better way to partition the disk).. but I 'fear' that a new installation will trigger 13.2 to be released... one day later.
* checking the changelogs every day now *
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
