Hi Muammar, 2011/10/13 Muammar El Khatib <[email protected]>: > There are some packages which depends on CEGUI that will fail to build because > of the change of the API. There are not that many, but still. Of course I > don't > want to ship obsolete things, but I don't want to break too many things.
If you think that there's a need for that in Debian, you can introduce a new package for versions with different APIs/ABIs, like [1]. Hopefully CEGUI doesn't need to ship so many versions, but maybe it could do with a couple of them. [1] http://qa.debian.org/[email protected] Anyway, from my POV it is to be expected that a new stable version of a package (not a snapshot, not a pre-release... but a proper stable upstream release of mature software) is shipped in Debian within weeks/months of the upstream release date. This is the case with hugely disruptive changes, like upgrading to GNOME-3 or KDE-4, when this affects to the normal workflow of thousands/millions of people that would prefer to resist the change; because it's generally understood (even if it's painful in many cases to move on) that eventually one has to do that anyway, if there's nobody who wants to take care of the software, and it's going to bitrot slowly. In this particular CEGUI case, you can follow (maybe too late now? maybe an idea for the future?) the route of having different package source versions happily living in the archive. You may not want to do that because of maintainance burden, and that's understandable. But then again, eventually one has to decide whether it's more beneficial/harmful to avoid having recent and maintained versions of a library, because of some projects lagging behind. I think that in cases like CEGUI the users ultimately prefer having the latests versions, and that is the case of libraries used in usually very dynamic projects (instead of, say, raving for the new version of procmail or bsd-mainutils). Sorry if I sounded rough and rude in the first e-mail, but I sometimes feel that the Debian world moves at a pace that risks obsolecence every day, except for a few core packages. And "dying" because of inaction and fear of what changes might bring is a quite stupid/ironic way of "dying". Regards, and sincere thanks for your efforts. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
