From: Fridrich S. <fri...@bl...> - 2007-10-06 11:41:59
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, good people. It is not like there is a lot of new features added for the while. The QA action of Sum1 made 0.1.0 quite OK, so for the while there are not bugs reported. And also, the WPG importer in ooo-build version of OO.o was released officially only recently, so reports from Ubuntu, Debian, OpenSuse,... will start to come only little by little. Nevertheless, there has been some work done on build system where we are now able to cross-compile the library and the tools completely on win32. Moreover, some fixes were needed to make libwpg (and wpg2odg) build with the upcoming gcc 4.3. These changes are now in CVS. Nevertheless, I was reflecting about making a 0.1.1 release to ship also these small fixes to that different distros that use already the gcc 4.3 do not have to distribute patched versions. In the same token I was thinking to branch the library with a branch tag STABLE-0-1-0 that would then contain only API & ABI compatible fixes and so, HEAD could have new features like for instance the text support... Ariya, specially you, what is your take on this? Cheers Fridrich - -- Please avoid sending me Word, Excel or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHB3R1u9a1imXPdA8RAhRgAJ9f0tREPjgJoxw0+zv9/HjHLUGGBgCfQsO1 FTDg/DOXIP8cxWRxlikIYBQ= =gLCM -----END PGP SIGNATURE----- |
From: Ariya H. <ari...@gm...> - 2007-10-08 08:38:59
|
> Hello, good people. It is not like there is a lot of new features added > for the while. The QA action of Sum1 made 0.1.0 quite OK, so for the > while there are not bugs reported. And also, the WPG importer in > ooo-build version of OO.o was released officially only recently, so > reports from Ubuntu, Debian, OpenSuse,... will start to come only little > by little. Nevertheless, there has been some work done on build system > where we are now able to cross-compile the library and the tools > completely on win32. Moreover, some fixes were needed to make libwpg > (and wpg2odg) build with the upcoming gcc 4.3. These changes are now in CVS. Fantastic and thank you for that work! > Nevertheless, I was reflecting about making a 0.1.1 release to ship also > these small fixes to that different distros that use already the gcc 4.3 > do not have to distribute patched versions. In the same token I was > thinking to branch the library with a branch tag STABLE-0-1-0 that would > then contain only API & ABI compatible fixes and so, HEAD could have new > features like for instance the text support... Ariya, specially you, > what is your take on this? I couldn't agree more with that. As soon as you branch, I'd like to also fix and add few API documentation here and there. This would not break ABI at all. In addition, I'll prepare Perfectspot so that it's ready for its first release. Fridrich, I saw that you're using OpenSUSE build service. I want to do the same for building Perfectspot, however since you have your build service nicely up and running already (even for many different distros), would it make sense if you can try to build Perfectspot there, and then add me (username: 'ariya') as the user of your home project? I know it might be not that easy since it uses CMake, but I guess it is better to have the wpg stuff consolidated in one place rather one in yours and one in mine. What do you think? Regards, Ariya |
From: Fridrich S. <fri...@bl...> - 2007-10-08 20:50:44
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ariya, Ariya Hidayat wrote: > Fridrich, I saw that you're using OpenSUSE build service. I want to do > the same for building Perfectspot, however since you have your build > service nicely up and running already (even for many different > distros), would it make sense if you can try to build Perfectspot > there, and then add me (username: 'ariya') as the user of your home > project? I know it might be not that easy since it uses CMake, but I > guess it is better to have the wpg stuff consolidated in one place > rather one in yours and one in mine. What do you think? You have been just added to my home project. Please, quality and security first, I have a (bad) reputation to safeguard :-) Now, the thing is easy. You just upload a tarbal and a spec file for that package. The best would be if you tried to make a SPEC file and build an RPM on your machine. For older distributions, one will have to link with the KDE:Qt repository too, because we need quite recent QT4. I will try to bug our OOo SuSE packager whether he can throw some light my side. I don't know how busy he will be, so timeframe cannot be promised, but will do my best. BTW: I branched and destabilised HEAD just now :-) The good branch is STABLE-0-1-0 and will produce libwpg-0.1.x. Head is now producing libwpg-0.2.x and apart of the fact that it can eat all the nice food you blog about, it can eat children and other protected species. So, consume with moderation and precaution :-) Cheers Fridrich -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHCpgJu9a1imXPdA8RAgPwAKCEavJAWhWLu5Xb/HzkHzNvbU7bZACdF/zw IXuWRLrgjnS9gP1rNj8CjIo= =D5j3 -----END PGP SIGNATURE----- |
From: Ariya H. <ari...@gm...> - 2007-10-09 13:32:17
|
Fridrich, > You have been just added to my home project. Thanks! > Please, quality and security first, I have a (bad) reputation to safeguard :-) I will keep this mind. > Now, the thing is easy. You just upload a tarbal and a spec file for > that package. The best would be if you tried to make a SPEC file and > build an RPM on your machine. For older distributions, one will have to > link with the KDE:Qt repository too, because we need quite recent QT4. I > will try to bug our OOo SuSE packager whether he can throw some light my > side. I don't know how busy he will be, so timeframe cannot be promised, > but will do my best. On my own machines (OpenSUSE 10.2 and 10.3), I have built the RPMs without problem. I guess it is then a matter of uploading the files to the build service and see whether it builds cleanly on other distros. I'll wait until I make its first 0.1 release. > BTW: I branched and destabilised HEAD just now :-) The good branch is > STABLE-0-1-0 and will produce libwpg-0.1.x. Head is now producing > libwpg-0.2.x and apart of the fact that it can eat all the nice food you > blog about, it can eat children and other protected species. So, consume > with moderation and precaution :-) So, you branched it quickly :-) While we're on that: (1) does make it sense if we include simplified ODGGenerator (which outputs e.g. context.xml only) also inside libwpg (so that wpg2odg is just a thin wrapper)? (2) Also, what is the plan regarding OOO stuff inside wpg2odg module? Is it going to disappear because you have integrated in Novell edition of OOo afterall? Regards, Ariya |