LinuxQuestions.org
View the Most Wanted LQ Wiki articles.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 03-01-2010, 01:29 PM   #1
letitgo
Member
 
Registered: Jul 2003
Location: New Orleans
Distribution: Slackware 13.0
Posts: 111
Blog Entries: 1

Rep: Reputation: 15
Slack-current change logs--changeless in Feb?


I suppose this comes under the heading of idle curiosity...

I've noticed that the Slackware-current change logs have had
no entries since Jan 31, 2010. Since it is March now, this
has caused me to wonder if everything's alright with Pat V.
and the development of the next version of Slackware.

--Lawrence
 
Click here to see the post LQ members have rated as the most helpful post in this thread.
Old 03-01-2010, 01:31 PM   #2
samac
Senior Member
 
Registered: Mar 2004
Location: Westray, Orkney
Distribution: Slackware64-14.1 (multi-lib) KDE 4.11.4
Posts: 1,422

Rep: Reputation: 137Reputation: 137
This is an example of just how stable Slackware is. I believe there are some fairly major changes being developed at the moment but that they will not hit current until they are ready.

samac
 
Old 03-01-2010, 01:56 PM   #3
GazL
Senior Member
 
Registered: May 2008
Posts: 3,440

Rep: Reputation: 959Reputation: 959Reputation: 959Reputation: 959Reputation: 959Reputation: 959Reputation: 959Reputation: 959
Eric touched on this in a blog posting a few days back:
http://alien.slackbook.org/blog/slac...alling-or-not/

It sounds like there's lots going on in private, but it would seem that the team want to keep us in the dark till they've finished (much like what happened with the 64bit version).

I can understand that some changes take bucket loads of time and effort, identifying build orders, bugs, and lots of other stuff like that, but I don't understand why they're also being so tight lipped about what they're working on.

If this trend towards secrecy continues then it sounds like the end of current as we've known it, and taken to the extreme we might end up only getting to see current when it hits 'beta'/'release candidate' stage like the other commercial distros do things.

I respect the teams choice to approach Slackware development however they want, it is their project after all, but this recent trend towards secrecy does make me a little uncomfortable about the future.
 
Old 03-01-2010, 02:08 PM   #4
samac
Senior Member
 
Registered: Mar 2004
Location: Westray, Orkney
Distribution: Slackware64-14.1 (multi-lib) KDE 4.11.4
Posts: 1,422

Rep: Reputation: 137Reputation: 137
Quote:
If this trend towards secrecy continues then it sounds like the end of current as we've known it, and taken to the extreme we might end up only getting to see current when it hits 'beta'/'release candidate' stage like the other commercial distros do things.
I disagree, it would be mad to allow major structural changes to be released until they are in a state that is at least able to be used. Then release it to current to catch the elusive bugs. As I understand it Slackware is not a community led project, but it is a well led project with a good community. I am happy to see it done this way.

samac
 
Old 03-01-2010, 02:12 PM   #5
mRgOBLIN
Slackware Contributor
 
Registered: Jun 2002
Location: New Zealand
Distribution: Slackware
Posts: 999

Rep: Reputation: 227Reputation: 227Reputation: 227
Will you junkies please calm down =)

Nothing is wrong...

It's getting close...

It takes time...

It's not a secret...

There is no spoon...
 
2 members found this post helpful.
Old 03-01-2010, 02:17 PM   #6
SpelledJ
Member
 
Registered: Jun 2006
Location: Birmingham, AL
Distribution: Slackware64-13.1, 12.1
Posts: 119

Rep: Reputation: 20
Eric also mentions the behind-the-scenes work in this post here.

I wouldn't read too much into the "secrecy" of what they're working on. We know that KDE 4.4 has issues with inclusion in Slackware due to its new dependency on policykit. I'm assuming that they're working on how to get around that dependency that doesn't require introducing PAM or creating a new maintenance nightmare for every future version of Slackware with KDE >4.4.

Pat has historically communicated chiefly through changelog updates. The development team knows that they've got a lot more users running -current than ever before because of KDE 4.3. If we got daily or weekly snapshots of work-in-progress KDE 4.4 builds, as well as the other packages they're modifying to make it work, -current would probably stay broken. So, we haven't gotten many changelog updates and therefore not a lot of communication from Pat.

I realize that -current comes with no guarantees on stability, but I appreciate that they're not pushing out half-finished updates just so we can see what's going on. The 1-31-10 stopping point has been very stable for me. I was worried about when would be a good time to burn a DVD of -current with Eric's mirror-slackware-current script, and early February turned out to work well.
 
Old 03-01-2010, 02:17 PM   #7
samac
Senior Member
 
Registered: Mar 2004
Location: Westray, Orkney
Distribution: Slackware64-14.1 (multi-lib) KDE 4.11.4
Posts: 1,422

Rep: Reputation: 137Reputation: 137
Please mRgOBLIN sir please feed my habit, I need what you, Pat, Eric, Robbie and the others feed us. PLLEEEEEAAAAAASSSEEEE!!!!

samac
 
0 members found this post helpful.
Old 03-01-2010, 02:24 PM   #8
GazL
Senior Member
 
Registered: May 2008
Posts: 3,440

Rep: Reputation: 959Reputation: 959Reputation: 959Reputation: 959Reputation: 959Reputation: 959Reputation: 959Reputation: 959
You misunderstand me Samac. I don't want to see the changes before they're ready. I'm quite happy to wait however long it takes, but I wouldn't mind knowing what they're working on at a 'headline' level, so I can make sure I'm prepared for when the changes finally show up.

Are they working on KDE4.4 with policykit/consolekit? Is it a new X11 version that's taking up the time, a new gcc/libc, update to the latest kernel, a brand new package-manager with dependencies? (YIKES!!) Are they adding SELinux and creating a policy for it? Stuff like that.
 
Old 03-01-2010, 02:33 PM   #9
GazL
Senior Member
 
Registered: May 2008
Posts: 3,440

Rep: Reputation: 959Reputation: 959Reputation: 959Reputation: 959Reputation: 959Reputation: 959Reputation: 959Reputation: 959
Quote:
Originally Posted by mRgOBLIN View Post
Will you junkies please calm down =)

Nothing is wrong...

It's getting close...

It takes time...

It's not a secret...

There is no spoon...
lol. At least we're still interested.
It's when we stop asking questions you have to worry!

 
Old 03-01-2010, 02:34 PM   #10
samac
Senior Member
 
Registered: Mar 2004
Location: Westray, Orkney
Distribution: Slackware64-14.1 (multi-lib) KDE 4.11.4
Posts: 1,422

Rep: Reputation: 137Reputation: 137
OK GazL that would be quite good as, after all, Slackware is too damn stable and we need something to discuss at great length of the forum. Maybe someone should start a sweepstake thread and then the cat population of Oldham would have to worry again.

samac
 
Old 03-01-2010, 02:37 PM   #11
mRgOBLIN
Slackware Contributor
 
Registered: Jun 2002
Location: New Zealand
Distribution: Slackware
Posts: 999

Rep: Reputation: 227Reputation: 227Reputation: 227
Quote:
Originally Posted by GazL View Post
Are they working on KDE4.4 with policykit/consolekit?
Nope

Quote:
Originally Posted by GazL View Post
Is it a new X11 version that's taking up the time, a new gcc/libc, update to the latest kernel, a brand new package-manager with dependencies? (YIKES!!) Are they adding SELinux and creating a policy for it? Stuff like that.
I'll give that 5 out of 10 since you didn't mention Gnome3 or a graphical installer =)
 
Old 03-01-2010, 02:50 PM   #12
samac
Senior Member
 
Registered: Mar 2004
Location: Westray, Orkney
Distribution: Slackware64-14.1 (multi-lib) KDE 4.11.4
Posts: 1,422

Rep: Reputation: 137Reputation: 137
Quote:
I'll give that 5 out of 10 since you didn't mention Gnome3 or a graphical installer =)
I thought Pat was re-branding Windows Vista with a Penguin/Bob logo and offering it as the best operating system in the world ever!

samac
 
Old 03-01-2010, 02:51 PM   #13
GazL
Senior Member
 
Registered: May 2008
Posts: 3,440

Rep: Reputation: 959Reputation: 959Reputation: 959Reputation: 959Reputation: 959Reputation: 959Reputation: 959Reputation: 959
hehe. Yep, I pretty much knew it wasn't 4.4 as it's already been hinted in several places that 4.3.5 will be the KDE for the next release, which is fine by me.

I thought about adding Gnome to that list, but I thought it was already getting far too silly as it was. I also didn't include PAM as that would have just been ridiculous!


Mind you, I don't know what I'm worried about. I normally just run 'stable' anyway.

Last edited by GazL; 03-01-2010 at 02:52 PM.
 
Old 03-01-2010, 03:50 PM   #14
sahko
Senior Member
 
Registered: Sep 2008
Distribution: Slackware
Posts: 1,041

Rep: Reputation: Disabled
Quote:
Originally Posted by letitgo View Post
I suppose this comes under the heading of idle curiosity...

I've noticed that the Slackware-current change logs have had
no entries since Jan 31, 2010.
I think its quite reasonable to be extra cautious with large updates in current furthermore now that the branch seems to be picked up by many more users than in the past, mostly KDE users, who are "sacrificing stability" for the extra features the newer KDE versions provide.
 
Old 03-01-2010, 04:23 PM   #15
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,313

Rep: Reputation: Disabled
One advance warning:

When the new Slackware batch hatches, and all of you apply your patches, be extra careful if you are running Slackware64-current with multilib and/or my KDE 4.4.0 packages on top of Slackware-current.

There will be some package upgrades from my end to reflect the new state of -current. I'll post the details on my blog once the trigger has been pulled.

Eric
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Slack-Current kaudiocreator Default encoder:WAV Can't be change blue900 Slackware 4 07-19-2009 11:34 PM
Slackware-Current (Feb 9) with HTTP/FTP installer, and SSHD. theoffset Slackware 3 02-09-2008 12:04 PM
updating Slack 10.2 with slack-current isos nacha Slackware 2 06-02-2006 08:52 PM
current Slack-Current giving troubles? r_jensen11 Slackware 5 02-02-2004 05:08 PM
From the Slackware-Current Change.log - Slack 9.1 shepper Slackware 0 09-12-2003 08:33 PM


All times are GMT -5. The time now is 06:09 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration