FS#2103 - fluxbox-devel SHOULD be moved to extra
Attached to Project:
Arch Linux
Opened by dtw (dibblethewrecker) - Sunday, 30 January 2005, 12:32 GMT
Last edited by Tobias Kieslich (tobias) - Tuesday, 08 February 2005, 10:11 GMT
Opened by dtw (dibblethewrecker) - Sunday, 30 January 2005, 12:32 GMT
Last edited by Tobias Kieslich (tobias) - Tuesday, 08 February 2005, 10:11 GMT
|
Details
Based on extensive discussion in the forum it is high time
that fluxbox-devel was moved to extra rather than fluxbox
0.1.14
on the fluxbox.org webpage it clearly states that fluxbox-dev is stable and maintained, whereas fluxbox 0.1.14 is unmaintained and outdated. We feel the slow speed at which fluxbox-devel is updated is due to it's postion in unstable and we are frustrated by this senseless situation. Refs: http://www.fluxbox.org/ http://bbs.archlinux.org/viewtopic.php?p=44284&highlight=fluxbox+devel+move http://bbs.archlinux.org/viewtopic.php?p=63957#63957 |
This task depends upon
0.1.14 Latest STABLE
0.9.12 Latest DEVEL
We all know that the "stable" tree is unmaitained and even doesn't build against gcc-3.4 - BUT - it just works! While there always have been troubles with the maintained "devel", such as the mysterious slit issue and most recently there have been issues with non-antialiased fonts. Now here come my arguments:
- some people still use fluxbox stable, I don't wanna lit them on and remove it
- No maintainer moves a *-devel package to extra, this is what unstable is for
- Finally it's not too much trouble to have unstable activated; extra or unstable it's in the repos anyway
Remark about update speed:
I was very busy in January and did not update any of my packages, neither from extra nor from unstable. So this was just coincident.
Open for flame :)
- arch removes the gcc3.3 combat package from gcc, the fluxbox won't start anymore
- there is a major security related issue in fluxbox, and we can't fix it cuz it won't build with current dev tools (compiler issue mainly)