what about leaving x11/win32 backend in uppsrc, but placing it in a seperate package there, which gets selected by default...
Correct, but impractical. It would add two packages two packages to any application - more packages -> less overview.
Quote:
moving Framebuffer in uppsrc wouldnt make much sense for a simple reason..as standalone it doesnt serve much..it always needs at least one final FB backend to compile..
So what? The only reason to keep Framebuffer from uppsrc is because it is not mature enough IMO.
In every case, I am now only resolving the current release - there I would go reference path. In future we can decode otherwise.
Members
Pages
Help
Register
Login
Home
