Il sabato 27 settembre 2008 01:29:09 Aaron J. Seigo ha scritto:
> hi everyone =) Hi Aaron. > > in the 4.1 branch, a set of changes was made to libkdcraw which consisted > of a substantial rewrite of the library that caused a change in ABI and a > change in the .so name. > > i assume this change was made in the 4.1 branch because people are > developing against the 4.1 branch of kdegraphics. > > unfortunately, such changes in ABI and features aren't allowed in the > stable branch after it's initial ".0" release. > > these change are fine, indeed welcome, in trunk/, but the changes will need > to be reverted in the 4.1 branch. As kipi project coodinator, apologize for that. We're new to kde core policy and we knew that we could have made mistakes :/. > we can always require the new version of the library for specific > applications, and we (kdegraphics people) coul even do a release of the new > library before 4.2 happens. > > before i just went off reverting things, however, i felt it was proper to > first discuss it here (and hopefully the committer of those changes can > revert it from the 4.1 branch themselves). 4.1.2 is due to be released > shortly, so taking care of this in a timely fashion is important.. Who ever has done that, i believe has been pushed by distro maintainers, since those changes were important to build digikam. Most distros, infact, ship kde 4.1.x and they could not have digikam. In mandriva we backported libkdcraw from trunk, so i believe others can do the same. We could add a point to the next code sprint we're preparing, e.g. how to get ABI unchnaged, for stable branches... maybe that requires some code changes, not sure, maybe not. Thanks for pointing us our mistakes, and not have reverted them silently. Angelo _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Angelo Naselli wrote:
> Most distros, infact, > ship kde 4.1.x and they could not have digikam. In mandriva we backported > libkdcraw from trunk, so i believe others can do the same. That would be an unfortunate choice and burdon to put onto distros. I'd much prefer if it didn't come to that. It's a wee bit of a shame that libkdcraw (and others) was consumed into kdegraphics... if it had remained an external dependency, this likely would have been less of an issue. -- Rex _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
lunedì 29 settembre 2008 alle 16:24, Rex Dieter ha scritto:
> Angelo Naselli wrote: > > > Most distros, infact, > > ship kde 4.1.x and they could not have digikam. In mandriva we backported > > libkdcraw from trunk, so i believe others can do the same. > > That would be an unfortunate choice and burdon to put onto distros. I'd > much prefer if it didn't come to that. > It's a wee bit of a shame that libkdcraw (and others) was consumed into > kdegraphics... if it had remained an external dependency, this likely would > have been less of an issue. Well that's not what we thought when we chose that. In my opinion we could have put into only libkipi, but i believe Gilles made what was right at that time. We need all the help, and the best way to get is involve more developers... What we need, of course, is to try not to make our stable releases - i mean digikam and kipi-plugins - not depending on trunk. But i understand digikam 0.10.0 and kipi-plugins are not final, just beta... Angelo _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel signature.asc (204 bytes) Download Attachment |
Free forum by Nabble | Edit this page |