Re: KDE SC 4.10
On 21/04/13 00:04, Modestas Vainius wrote:
>
> There is a way to do this - backports. It is an official service as of wheezy.
> However, I see the main problem here - noone is interested in actually doing
> the necessary work and invest their days/weeks of time to make it reality.
> Debian developers typically use unstable while stable or testing is already
> good enough for less tech-savvy users or those who do not care about versions.
>
> Backporting a single package is one thing, backporting 100 tightly related
> source packages is another. And it's more than 100 times harder.
Hi,
I actually understand this. But theses are, IMO, choices made, rather
than any restrictions in man power or tools available. Simply it should
be just "backports" from the beginning, but there is more to it.
There is a paradigm here, however I'm so far below the lowest rung of
the debian hierarchy is that all I can do is somehow allude to people
figuring it out for themselves. Because I know that saying "Give up
developing high level application packages for debians main release
cycles and give them their own repos and/or release cycles" won't get me
far.
Its a time cycle issue (speed). For example, user interactive
applications gain features, fix bugs, create bugs etc. They develop
differently. Critical System libraries and applications are more likely
to require a need to remain stable and have less (if any) drastic
changes to API's over a greater cycle.
I care about a stable Operating System, I care much less about the 1000s
of packages that run on top of it. To me debian is buried by it all (its
the bane of most distros).
In my spare time. I'm playing with some ideas on a build system, where,
roughly, suites (e.g. system, gnu base, misc apps, gnome, KDE),
including meta packages and sub packages - are all partitioned off.
i.e. <some_package>'s "system" dependency on version "2.14" for "glibc"
does not exist in the "stable" release suite for "system"". This is not
a build error, this is a failed package dependency attribute db entry.
Just adding another dimension to the build process. I hope someone else
does it before me so I can do other stuff. But I'm majorly enthusiastic
about it.
All the best for now.
Jules.
Reply to: