Can't we just think of vl 5.8 as a fine finished product and start with VL 6? In the meantime we can just continue using our normal 5.8 installs without having a new vector-5.8.6 repo or weird problems of packages working on 5.8 but not on 5.8.6 or the other way around.
Oh well, I suppose I might be impatient for the slack 12 goodiness in that fine VL sauce
I second that.
The new Slackware 12 packages solve practically all the problems that we were having in the GTK/Xorg/Kernel debate, so why not get started with the Slack12 based VL6.0 now?
Anyway, on the VL 6.0 topic, whats the status on more VL specific stuff like VL-hot and the new VASM? HAL is included by default in Slackware 12, but its not as old-hardware-friendly as VL-hot is...so any idea about what VL6 will have?
What about laying out other objectives for areas like:
- Repo layout and maintenance (guidelines about what to do with major package upgrades - should they even exist.)
- Packaging and packaging standards (maybe a more up-to-date how-to with info on scripting would be cool and of course Moe's awesome package builder.)
- Wireless networking integration (I like Wifi-radar, but it would be cool to modify it/create something new to fit into VL seamlessly, in a similar way that NetworkManager does for Ubuntu/Suse/RHEL, but without the bloat and resource hogging).
- Power management tools (this includes suspend support)
- Extra drivers (there are lots of drivers and firmware, especially for wireless cards that can be added to the default kernel package, or included as separate packages)
- ISO size limit (1 CD policy or...?)
- Attention to conflicting Slackware packages (eg: libiconv)
- **insert your ideas here**
Also whats the take on some more radical things like Initng