You are not logged in.
Pages: 1
The latest version of Conky in Arch is 1.5.1-1, whereas a new version 1.6.0 has already been released.
I was surprised to see that the Debian testing has been updated with 1.6.0 already whereas Arch hasnt. And Arch is the one which is a rolling release.
Forgive my rant...coz I am really looking forward to the 1.6.0 version because the changelog says that it fixed some bugs related to mpd and if clauses. I guess I will just have to install from source for the time being.
Since we are on the topic :
Who updates the packages that are in the [core] and [extra] repos? Developers?
I know that the packages in the AUR can be "owned" by some users and they are responsible for updates and maintenance. Are the packages in [core] and [extra] handled similarly by developers? How do they keep track of the thousands of packages and how do they check whether a new version of the said software has been released or not?
Last edited by Inxsible (2008-08-17 06:12:55)
Offline
Well, it has been 11 days since pekwm 0.1.7 released, but still not followed in Arch..
Offline
If you really want the newer versions, then it's really easy to build them by yourselves! Maybe it's even enough to change the version number and of course the md5sums. I tried it out, works perfectly
Maybe there are some new configure parameters, but with those in the PKGBUILD it works fine here.
Never forget, Arch is a community driven distribution, which means, that it's also our job to tell the devs about newer versions of applications and you should be able to build it by yourself, if the dev is too slow for you.
Offline
Offline
I mean, Arch wants to be up to date, so it's not wrong to say, I want the newer version. But as I said, abs makes it so amazingly easy, so you do not depend on the binary repos. Anyway, if the new version of conky really fixes so many bugs, then it should be updated asap
Offline
You have in AUR several packages that gives you 1.6. I'm not sure how well they work, I do not use AUR if I really don't have to. And conky 1.5 works fine for me.
We met up with the aliens and guess what? They have no word for fluffy!
Offline
I've been using conky-svn from aur for a while now, no real problems except some other issue with xfwm effects and conky overlapping/flickering.
ARCH64 | XMonad | Configs | myAURpkgs | ArchWiki Contribs | Screenies
Offline
there you go, conky 1.6.1 with nvidia support:
http://aur.archlinux.org/packages.php?ID=19156
Last edited by adamruss (2008-08-17 12:23:36)
CPU: MacBook Pro 5,5
TB: OSX 10.6 / Windows 7 / Ubuntu 9.10
Offline
Thanks for your replies..
But when I uploaded the PKGBUILD for conky 1.6.0, it was deleted by a dev/mod and he quoted me the AUR User Guidelines which said
When submitting a package, observe the following rules:
* Check [core], [extra], [unstable], and [community] for the package. If it is inside any of those repositories in ANY form, DO NOT submit the package (if the current package is broken or is lacking an included feature then please file a bug report in FlySpray).I totally agree with that dev/mod for deleting the package that I uploaded, because no one really wants multiple versions of the same package in the repos. So that's why I asked the question in my first post..how do the devs keep track of the new versions that get released?
Do the users of the said package tell the devs to update or something?
Offline
It is already marked as out of date (in the online interface to packages there is a specific button). Any dev has its priority list and may be on vacation (it is summer). Abs is there to let you compile VERY easily in a few seconds any version of conky you like modifying two or three chars in the PKGBUILD (the version number) and nothing else.
Mortuus in anima, curam gero cutis
Online
Pages: 1