Apparently you're referring to an *Arch* package of 1.7.0 which oozed out on 2011-03-21. However, the last released upstream file on Sourceforge is Beta 2 of 1.7.1 back on 2010-11-20. Also, to quibble with your words, Pat wrote "development has ceased", not "discontinued", and the difference between those words is illustrated by the announcement made on 2010-09-14 which can be found at https://launchpad.net/wicd/+announcement/6738 -- "Wicd development stalled"

But the difference between "ceased" and "discontinued" is de minimis when there have been only 17 code commits in the last year and six since 1.7.1b2.

For the record I happen to prefer wicd too, or at least its UI anyway, and I'm grateful for what the developers have been able to give us until now.

2 members found this post helpful.

Ah, sorry for the trouble then. Kind of a shame, wicd is pretty cool.

ftp://ftp.osuosl.org/pub/slackware/s...nt/UPGRADE.TXT

shouldn't that be:

1 members found this post helpful.

Yeah seems that part is leftover from 13.1

It seems that yesterday Pat update Slackware ARM with kernel 2.6.38.2, here.

So it's possible it will Slackware 13.37 have kernel 2.6.38.2?

As far as I know it's actually Stuart Winter behind ArmedSlack so I don't think this update has any bearing on Slackware itself. I know Stuart was originally responsible but I don't know if he's still the maintainer. Stuart said this on the mailing list some time ago which may be relevant :

1 members found this post helpful.

Thanks for the explain

I thought that I read somewhere that they were trying to make all the versions identical but for different architectures. So 2.6.38.2 might be in the running.

BUT....

Much more importantly I've just had six days off and was hoping to have a shiny new fresh install of Slackware64-13.37 (multi-lib). Hopefully we will have another release candidate soon or, better still, the final release.

samac

F******k!!! I can't wait any longer... I feel awful... if Slackware 13.37's not released in the next month then I'm gonna install a cracked version of Windoze on my slackbox and convert every file I have to an Office Open XML variant!

Well you could always upgrade to -current now, get something that is probably 99% the same as what 13.37 will turn out to be and as an added bonus you may even contribute to its stability by finding any remaining bugs. Win win!

Oh.. it is: so much bigger..

I used WICD until now. I'm (trying) to configure NetworkManager as we speak. Via sbopkg..

- NetworkManager
- ORBit2
- libtasn1
- Gconf
- Gnome-keyring
- pptp
- Network-pptp
- Network-applet

That's a lot o stuff.. (okay: I need NetworkManager only if I wish to CLi, but to get the about a gui, I need the applet, and the applet needs Gnome-keyring, which depends on Gconf, ORBit2 and Libtasn1,... I just wonder if that's worth it.

hmm. pitty wicd's development has ceased, but I already think it is indeed way <<<< that NetworkManager..

*Back on Topic*

leet: It will be worth the wait.
*and remember: Slackware is like coffee: The longer it takes to fill your cup, the better the quality of the tar provided! ( http://en.wikipedia.org/wiki/Tar_%28tobacco_residue%29 -> note the pipe-smoking-tar-providing-penguin )

If you're building stuff like network-manager-applet with quite a few dependencies using the wonderful Sbopkg I highly recommend getting the queue files - they make this kind of build very easy and are a great help with any build with lots of dependence requirements.

1 members found this post helpful.

That takes care of the build, but what would you recommend for the lingering feelings of nausea and self-loathing?

1 members found this post helpful.

A few drinks, and a session with the Emacs psychotherapist.

1 members found this post helpful.

Yeah! But not quite as effective as a session with the Vi psychologist.

samac