Re: Packaging of Calligra for PA
Am Sonntag, 17. Februar 2013, 21:37:35 schrieb Thomas Pfeiffer: On Sunday 17 February 2013 13:56:58 Maurice de la Ferté wrote: The calligramobile looks a bit broken because I'm not able to open any document by choosing with it. Calligra Mobile is not really maintained afaik and yes, it's pretty broken in PA. It was made specifically for Meego Harmattan, and it shouldn't actually be built anywhere outside of it. There is no Calligra Mobile, there is only Calligra Active these days :) (Yes, the icon name in the desktop file of Calligra Active is still calligramobile, that name would need to be updated. Surely because the icon is not used anyway in the current design of Plasma Active) Cheers Friedrich ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: Packaging of Calligra for PA
Hi Maurice, Am Sonntag, 17. Februar 2013, 16:23:15 schrieb Maurice de la Ferté: On 17.02.2013 14:43, Friedrich W. H. Kossebau wrote: Am Sonntag, 17. Februar 2013, 13:56:58 schrieb Maurice de la Ferté: On 17.02.2013 02:02, Friedrich W. H. Kossebau wrote: Am Samstag, 16. Februar 2013, 04:38:09 schrieb Maurice de la Ferté: On 16.02.2013 03:21, Friedrich W. H. Kossebau wrote: 2. How is review done for spec/yaml changes? Best practice is - 'osc branch Project:KDE:Devel calligra' - checkout local copy of branched package - making changes - building local - pushing changes - building remote - reviewing rpmlint messages in logs - adding branching repos to test machine - installing branching packages on test machine - 'osc submitrequest branched project calligra Project:KDE:Devel' - asking for review on #active First trivial request is up, seems it works all for me :) Request is applied :) \o/ Okay, now that this is established I can get to serious changes :) Nothing in the pipe yet, but already thinking about how to best fix the incomplete registering for all supported mimetypes within the Calligra build system. Too late for 2.6.1, but than packagers can always still patch the released stuff ;) Next questions: Can I reuse that branch I created somehow? How do I ideally merge the changes from the official calligra package? Any request is just a diff between the branch to the official package, or? Yes you can reuse this branched project so long you are not deleting it. By sending submit requests via Web-Frontend you will see a checkbox about something like 'deleting after merge', which is enabled by default. This behaviour is disabled by using 'osc submitrequest' via command line. Seems it was not disabled for me. Or I did something else which I cannot remember :) A easy way to keep in sync with original package is following setup: 1. Branch a random package from the original project. By this you will get the repository setup and build dependencies from the original project. e.g. osc branch Project:KDE:Devel/cmake 2. Open project home:user:Project:KDE:Devel via Web-Frontend and enable repository publishing. Repositories -- Publish Flag -- All -- Explicity enable By this you are able to install the packages directly on your test machine 3. Open project home:user:Project:KDE:Devel via Web-Frontend and branch the package you like to modify/maintain. Packages -- Branch package from other project -- Name of original project: Project:KDE:Devel Name of package in original project: calligra Name of branched package in target project: [ ] Stay on current revision, don't merge future upstream changes automatically 4. Open project home:user:Project:KDE:Devel via Web-Frontend and delete random package again. Packages -- cmake -- Delete package By this setup you have all changes from original package plus the changes you are working on. Please note, by this merge conflicts can happen you have to solve on your own. Thanks. Currently preparing the 2.6.1 update as merge request, with some additional patches that enable the import filters for more formats, like docx, pptx, xslx, ... (because other than promoted on plasma-active.org Calligra Active so far refused to load docx and xlsx, due to hardcoded mimetype checks. oh promoters, please check what you claim!) waiting for the build to finish, then will test on the device. Expect a merge request tonight or later this WE :) Cheers Friedrich ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: Packaging of Calligra for PA
Hi, On 22.02.2013 23:01, Friedrich W. H. Kossebau wrote: Hi Maurice, Am Sonntag, 17. Februar 2013, 16:23:15 schrieb Maurice de la Ferté: On 17.02.2013 14:43, Friedrich W. H. Kossebau wrote: Am Sonntag, 17. Februar 2013, 13:56:58 schrieb Maurice de la Ferté: On 17.02.2013 02:02, Friedrich W. H. Kossebau wrote: Am Samstag, 16. Februar 2013, 04:38:09 schrieb Maurice de la Ferté: On 16.02.2013 03:21, Friedrich W. H. Kossebau wrote: 2. How is review done for spec/yaml changes? Best practice is - 'osc branch Project:KDE:Devel calligra' - checkout local copy of branched package - making changes - building local - pushing changes - building remote - reviewing rpmlint messages in logs - adding branching repos to test machine - installing branching packages on test machine - 'osc submitrequest branched project calligra Project:KDE:Devel' - asking for review on #active First trivial request is up, seems it works all for me :) Request is applied :) \o/ Okay, now that this is established I can get to serious changes :) Nothing in the pipe yet, but already thinking about how to best fix the incomplete registering for all supported mimetypes within the Calligra build system. Too late for 2.6.1, but than packagers can always still patch the released stuff ;) Next questions: Can I reuse that branch I created somehow? How do I ideally merge the changes from the official calligra package? Any request is just a diff between the branch to the official package, or? Yes you can reuse this branched project so long you are not deleting it. By sending submit requests via Web-Frontend you will see a checkbox about something like 'deleting after merge', which is enabled by default. This behaviour is disabled by using 'osc submitrequest' via command line. Seems it was not disabled for me. Or I did something else which I cannot remember :) A easy way to keep in sync with original package is following setup: 1. Branch a random package from the original project. By this you will get the repository setup and build dependencies from the original project. e.g. osc branch Project:KDE:Devel/cmake 2. Open project home:user:Project:KDE:Devel via Web-Frontend and enable repository publishing. Repositories -- Publish Flag -- All -- Explicity enable By this you are able to install the packages directly on your test machine 3. Open project home:user:Project:KDE:Devel via Web-Frontend and branch the package you like to modify/maintain. Packages -- Branch package from other project -- Name of original project: Project:KDE:Devel Name of package in original project: calligra Name of branched package in target project: [ ] Stay on current revision, don't merge future upstream changes automatically 4. Open project home:user:Project:KDE:Devel via Web-Frontend and delete random package again. Packages -- cmake -- Delete package By this setup you have all changes from original package plus the changes you are working on. Please note, by this merge conflicts can happen you have to solve on your own. Thanks. Currently preparing the 2.6.1 update as merge request, with some additional patches that enable the import filters for more formats, like docx, pptx, xslx, ... (because other than promoted on plasma-active.org Calligra Active so far refused to load docx and xlsx, due to hardcoded mimetype checks. oh promoters, please check what you claim!) waiting for the build to finish, then will test on the device. Expect a merge request tonight or later this WE :) request applied :) Great thanks, Maurice ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: Packaging of Calligra for PA
Hi,
On 17.02.2013 02:02, Friedrich W. H. Kossebau wrote:
Hi Maurice,
Am Samstag, 16. Februar 2013, 04:38:09 schrieb Maurice de la Ferté:
Hi,
On 16.02.2013 03:21, Friedrich W. H. Kossebau wrote:
Hi,
Am Dienstag, 12. Februar 2013, 13:25:39 schrieb Sebastian Kügler:
On Monday, February 11, 2013 22:42:08 Friedrich W. H. Kossebau wrote:
1. Step: Packaging setup
What do you recommend to me to try test the packaging?
I have available:
* ExoPC (as spread by Intel on the Berlin DesktopSummit)
* 64-bit desktop computer running OpenSuse Tumbleweed with some cores to
use
Reached the state where I can do packaging:
1. Installed Mer SDK
2. Revived my MeeGo.com account (password of course forgotten, and the
server did not sent out the new one for a few days, but at least today
finally) 3. Setup OSC locally
4, Checkout Project:KDE:Devel calligra
5. Build packages locally with
osc build --no-verify Mer_Core-next_CE_UX_PlasmaActive_i586 i586
So far everything worked :)
(modulo try error bumping on the way to get there, but no animals or
humans were hurt, minimal data loss, like when accidentally untaring the
SDK tarball in the own home directory, doh)
Notes are taken and will be added to the wiki, once I am sure of the
process.
Now the next questions:
1. Is the YAML file or the spec file used? (any good intro into YAML?)
The spec file is used, but it is generated and updated by yaml
Please note, spec an yaml file might be out of sync in calligra atm
- Command 'specify' will do the update job
- Mer SDK is using newer version as used at the moment
- Urls:
http://wiki.meego.com/Spectacle
http://wiki.meego.com/SDK/Docs/1.0/Packaging/Tutorial
- No doubt, starting with yaml will be a pain in the ass
- spec changes outside # ; # area get silently dropped
- specify will add or remote stuff from specfile depending on file
section
e.g. #%{libdir}libanything.so.* in file section creates a
ldconfig postinstall entry
e.g. # any path.desktop in file section creates a
desktop-file-install post install entry
...
- If help needed ask in #active or #mer
No pain yet, but than I have not done enough ;) Thanks, think I got how things
are done.
2. How is review done for spec/yaml changes?
Best practice is
- 'osc branch Project:KDE:Devel calligra'
- checkout local copy of branched package
- making changes
- building local
- pushing changes
- building remote
- reviewing rpmlint messages in logs
- adding branching repos to test machine
- installing branching packages on test machine
- 'osc submitrequest branched project calligra Project:KDE:Devel'
- asking for review on #active
First trivial request is up, seems it works all for me :)
Request is applied :)
3. Is there a way to run the PA shell from inside the Mer SDK and test the
locally created packages, with Xephyr or similar
I never tried to install PA into Mer SDK so I don't know, but I fear it
does not work.
Too bad :/ Especially as the ExoPC dies for me every few times, incl. broken
rpm database now and then. Sucks :(
(yes, happened also before I started to mess with packaging ;) )
Is that common behaviour? Or is my ExoPC broken?
Ouch, for me it sounds like a broken device too. I'm using the following
images
installed in VirtualBox and never faced a broken rpm database, it makes a
robust impression to me:
http://share.basyskom.com/plasma-active/deployment/wetab-exopc/tablet/mer/devel/weekly/
Therefor I followed the description on following URL with enable the
mous cursor: http://community.kde.org/Plasma/Active/Installation#Virtual_Box
Also I changed the /usr/share/kde4/config/kwinactiverc from 'Backend=OpenGL'
to 'Backend=XRender' to make compositing working again. I used 'vim'
from 'konsole'
for editing. Please note, do not click into the black window area
otherwise you will
get the virtual keyboard which will stuck till reboot by broken compositing.
If you are wondering why the desktop icons for calligra are missing,
they are
blacklisted inside /usr/share/kde4/config/active-blacklistrc and get
visible after
removing 'sheets,words,stage,calligramobile' from it (maybe restart is
needed).
I don't know why they are blacklisted, because sheets, words and stage makes
a very useful impression to me. The calligramobile looks a bit broken
because
I'm not able to open any document by choosing with it.
Cheers
Maurice
___
Active mailing list
Active@kde.org
https://mail.kde.org/mailman/listinfo/active
Re: Packaging of Calligra for PA
Am Sonntag, 17. Februar 2013, 13:56:58 schrieb Maurice de la Ferté: On 17.02.2013 02:02, Friedrich W. H. Kossebau wrote: Am Samstag, 16. Februar 2013, 04:38:09 schrieb Maurice de la Ferté: On 16.02.2013 03:21, Friedrich W. H. Kossebau wrote: 2. How is review done for spec/yaml changes? Best practice is - 'osc branch Project:KDE:Devel calligra' - checkout local copy of branched package - making changes - building local - pushing changes - building remote - reviewing rpmlint messages in logs - adding branching repos to test machine - installing branching packages on test machine - 'osc submitrequest branched project calligra Project:KDE:Devel' - asking for review on #active First trivial request is up, seems it works all for me :) Request is applied :) \o/ Okay, now that this is established I can get to serious changes :) Nothing in the pipe yet, but already thinking about how to best fix the incomplete registering for all supported mimetypes within the Calligra build system. Too late for 2.6.1, but than packagers can always still patch the released stuff ;) Next questions: Can I reuse that branch I created somehow? How do I ideally merge the changes from the official calligra package? Any request is just a diff between the branch to the official package, or? 3. Is there a way to run the PA shell from inside the Mer SDK and test the locally created packages, with Xephyr or similar I never tried to install PA into Mer SDK so I don't know, but I fear it does not work. Too bad :/ Especially as the ExoPC dies for me every few times, incl. broken rpm database now and then. Sucks :( (yes, happened also before I started to mess with packaging ;) ) Is that common behaviour? Or is my ExoPC broken? Ouch, for me it sounds like a broken device too. I'm using the following images installed in VirtualBox and never faced a broken rpm database, it makes a robust impression to me: http://share.basyskom.com/plasma-active/deployment/wetab-exopc/tablet/mer/de vel/weekly/ Therefor I followed the description on following URL with enable the mous cursor: http://community.kde.org/Plasma/Active/Installation#Virtual_Box Also I changed the /usr/share/kde4/config/kwinactiverc from 'Backend=OpenGL' to 'Backend=XRender' to make compositing working again. I used 'vim' from 'konsole' for editing. Please note, do not click into the black window area otherwise you will get the virtual keyboard which will stuck till reboot by broken compositing. Okay, thanks for the tip, possibly will have to change to that then if that problem does not stop to happen. If you are wondering why the desktop icons for calligra are missing, they are blacklisted inside /usr/share/kde4/config/active-blacklistrc and get visible after removing 'sheets,words,stage,calligramobile' from it (maybe restart is needed). I don't know why they are blacklisted, because sheets, words and stage makes a very useful impression to me. The calligramobile looks a bit broken because I'm not able to open any document by choosing with it. From what I understood from the recent discussion that is by purpose, i.e. by design of Plasma Active. CalligraActive should only be invoked as handler on given files, not offer a filedialog to select a file itself. The full desktop programs Sheets, Stage Words should not be launched or even available on PlasmaActive. But that is out of my playing field, topic for the PlasmaActive UX designers and Shantanu :) I just care for proper packaging. Which means one of the next steps would be also extending the build system to be able to just build the Sheets, Stage Words parts that are used by CalligraActive, but not also the desktop program shells. At least so far I understood that was matching the Active idea. Cheers Friedrich ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: Packaging of Calligra for PA
On Sunday 17 February 2013 13:56:58 Maurice de la Ferté wrote: If you are wondering why the desktop icons for calligra are missing, they are blacklisted inside /usr/share/kde4/config/active-blacklistrc and get visible after removing 'sheets,words,stage,calligramobile' from it (maybe restart is needed). I don't know why they are blacklisted, because sheets, words and stage makes a very useful impression to me. Have you tried to actually use them with touchscreen only? That's no fun, they're not adapted to touch at all. Touch-friendly versions will come eventually, but until then, we don't want users to get a bad impression from trying to use the desktop versions on a touch device. The calligramobile looks a bit broken because I'm not able to open any document by choosing with it. Calligra Mobile is not really maintained afaik and yes, it's pretty broken in PA. It was made specifically for Meego Harmattan, and it shouldn't actually be built anywhere outside of it. ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: Packaging of Calligra for PA
On Sunday 17 February 2013 14:43:03 Friedrich W. H. Kossebau wrote: \o/ Okay, now that this is established I can get to serious changes :) Nothing in the pipe yet, but already thinking about how to best fix the incomplete registering for all supported mimetypes within the Calligra build system. Too late for 2.6.1, but than packagers can always still patch the released stuff ;) Sounds promising! :) Which means one of the next steps would be also extending the build system to be able to just build the Sheets, Stage Words parts that are used by CalligraActive, but not also the desktop program shells. At least so far I understood that was matching the Active idea. Exactly, that's what we'd need. ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: Packaging of Calligra for PA
Hi, Am Dienstag, 12. Februar 2013, 13:25:39 schrieb Sebastian Kügler: On Monday, February 11, 2013 22:42:08 Friedrich W. H. Kossebau wrote: 1. Step: Packaging setup What do you recommend to me to try test the packaging? I have available: * ExoPC (as spread by Intel on the Berlin DesktopSummit) * 64-bit desktop computer running OpenSuse Tumbleweed with some cores to use Reached the state where I can do packaging: 1. Installed Mer SDK 2. Revived my MeeGo.com account (password of course forgotten, and the server did not sent out the new one for a few days, but at least today finally) 3. Setup OSC locally 4, Checkout Project:KDE:Devel calligra 5. Build packages locally with osc build --no-verify Mer_Core-next_CE_UX_PlasmaActive_i586 i586 So far everything worked :) (modulo try error bumping on the way to get there, but no animals or humans were hurt, minimal data loss, like when accidentally untaring the SDK tarball in the own home directory, doh) Notes are taken and will be added to the wiki, once I am sure of the process. Now the next questions: 1. Is the YAML file or the spec file used? (any good intro into YAML?) 2. How is review done for spec/yaml changes? 3. Is there a way to run the PA shell from inside the Mer SDK and test the locally created packages, with Xephyr or similar? Cheers Good night Friedrich ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: Packaging of Calligra for PA
Hi,
On 16.02.2013 03:21, Friedrich W. H. Kossebau wrote:
Hi,
Am Dienstag, 12. Februar 2013, 13:25:39 schrieb Sebastian Kügler:
On Monday, February 11, 2013 22:42:08 Friedrich W. H. Kossebau wrote:
1. Step: Packaging setup
What do you recommend to me to try test the packaging?
I have available:
* ExoPC (as spread by Intel on the Berlin DesktopSummit)
* 64-bit desktop computer running OpenSuse Tumbleweed with some cores to
use
Reached the state where I can do packaging:
1. Installed Mer SDK
2. Revived my MeeGo.com account (password of course forgotten, and the server
did not sent out the new one for a few days, but at least today finally)
3. Setup OSC locally
4, Checkout Project:KDE:Devel calligra
5. Build packages locally with
osc build --no-verify Mer_Core-next_CE_UX_PlasmaActive_i586 i586
So far everything worked :)
(modulo try error bumping on the way to get there, but no animals or humans
were hurt, minimal data loss, like when accidentally untaring the SDK tarball
in the own home directory, doh)
Notes are taken and will be added to the wiki, once I am sure of the process.
Now the next questions:
1. Is the YAML file or the spec file used? (any good intro into YAML?)
The spec file is used, but it is generated and updated by yaml
Please note, spec an yaml file might be out of sync in calligra atm
- Command 'specify' will do the update job
- Mer SDK is using newer version as used at the moment
- Urls:
http://wiki.meego.com/Spectacle
http://wiki.meego.com/SDK/Docs/1.0/Packaging/Tutorial
- No doubt, starting with yaml will be a pain in the ass
- spec changes outside # ; # area get silently dropped
- specify will add or remote stuff from specfile depending on file
section
e.g. #%{libdir}libanything.so.* in file section creates a
ldconfig postinstall entry
e.g. # any path.desktop in file section creates a
desktop-file-install post install entry
...
- If help needed ask in #active or #mer
2. How is review done for spec/yaml changes?
Best practice is
- 'osc branch Project:KDE:Devel calligra'
- checkout local copy of branched package
- making changes
- building local
- pushing changes
- building remote
- reviewing rpmlint messages in logs
- adding branching repos to test machine
- installing branching packages on test machine
- 'osc submitrequest branched project calligra Project:KDE:Devel'
- asking for review on #active
3. Is there a way to run the PA shell from inside the Mer SDK and test the
locally created packages, with Xephyr or similar
I never tried to install PA into Mer SDK so I don't know, but I fear it
does not work.
Cheers,
Maurice
aka mdfe_ on #active
___
Active mailing list
Active@kde.org
https://mail.kde.org/mailman/listinfo/active
Re: Packaging of Calligra for PA
On Monday, February 11, 2013 22:42:08 Friedrich W. H. Kossebau wrote: 1. Step: Packaging setup What do you recommend to me to try test the packaging? I have available: * ExoPC (as spread by Intel on the Berlin DesktopSummit) * 64-bit desktop computer running OpenSuse Tumbleweed with some cores to use In MeeGo times I had some chrooted image on my laptop where I tried the packaging locally before I pushed any changed to OBS. I scanned the PA wiki pages shortly for something similar, but did not find any real notes about packaging. So how do you do the packaging? Ah, just discovered that Mer seems to have continued that approach to a devel env: https://wiki.merproject.org/wiki/Platform_SDK And Mer also would be the most interesting platform to me, so would favor to test/do packaging there. Yep, exactly that. :) And how are packaging rules ported between the different platforms (Mer, MeeGo, Balsam/OpenSuse 12.1, other?) supported ATM? Easy: they are not shared. We usually do the packaging on top of Mer, and have other distros pick it up, possibly being inspired by the Mer packaging. Mer is the only system we do QA for, with our limited resources. Now please your hints. Will try to summarize and put up into the wiki, once I have a picture. If you've questions, #active and #mer are useful resources on IRC, so is this list (as you've discovered). Cheers, -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: Packaging of Calligra for PA
Hi Marco all, Am Freitag, 8. Februar 2013, 16:23:26 schrieb Marco Martin: On Friday 08 February 2013, Friedrich W. H. Kossebau wrote: Heya, I would like to do my little bit of contributing to PA, by the means of caring for the packaging of Calligra. Given that I meanwhile got knee-deep into Calligra code and project :) I also have an interest to make it shine as much as possible on PA. awesome, that would be very appreciated :D Thanks for you replies, happy to see that I am running through doors wide open :) Well, if am running... Sorry, did not make it to #active during the WE, too busy with other stuff (at least Calligra related :) ). At least some questions now by email, see below: So I would e.g. care to have the latest (now 2.6.0, not 2.6 beta1) stuff packaged and also have the CSV import filter properly installed ;) (Would for me also yield some experience how packagers experience the Calligra code dumps) Some may remember I had been involved in the community packaging of KDE software for MeeGo, so you can expect some level of experience. yeah, remember at the berlin sprint back then ;) (btw your user still has all permissions on https://build.pub.meego.com/project/show?project=Project%3AKDE%3ADevel so all should be ready to go) Interesting to see that the MeeGo OBS is still alive, and also usable for PA :) Who is running it, some good folks at Intel/LinuxFoundation? About Calligra, at the moment it builds correctly, regarding how should be built, what version or if the package splitting could need some revision, here you probably know more ;) Yes, especially the package splitting will be interesting to look at with a packager hat on, just had a look at the OpenSuse one and saw that packagers definitely need more info :) Shantanu and me should be able to brush things up here, so everything worthwhile will be packaged, but nothing more. E.g., would the thumbnailer plugin also be interesting to PA? It supports also most formats for which there are import filters (incl. MS ones). just as other information potentially useful. I think in the past some work on calligra active (either in code or packaging) has been done by Shantanu, Maurice, and iirc Leinir recently did some experients with the branch with krita sketch, so may help some coordination there as well Yep, will try to be another good ambassador of Calligra here, next to Shantanu :) Just do not expect any PA-related programming from me, am not yet into QML and also busy with high-priority coding elsewhere (Calligra, Okteta, Kasten). Also no bug-fixing. Just packaging. Might change later this year :) Now to the topic: 1. Step: Packaging setup What do you recommend to me to try test the packaging? I have available: * ExoPC (as spread by Intel on the Berlin DesktopSummit) * 64-bit desktop computer running OpenSuse Tumbleweed with some cores to use In MeeGo times I had some chrooted image on my laptop where I tried the packaging locally before I pushed any changed to OBS. I scanned the PA wiki pages shortly for something similar, but did not find any real notes about packaging. So how do you do the packaging? Ah, just discovered that Mer seems to have continued that approach to a devel env: https://wiki.merproject.org/wiki/Platform_SDK And Mer also would be the most interesting platform to me, so would favor to test/do packaging there. And how are packaging rules ported between the different platforms (Mer, MeeGo, Balsam/OpenSuse 12.1, other?) supported ATM? Now please your hints. Will try to summarize and put up into the wiki, once I have a picture. Cheers Friedrich ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: Packaging of Calligra for PA
On Sunday 10 February 2013 11:13:15 you wrote: Well the Calligra libs and the rendering bits like flake are separate and shared by all Calligra applications. However, when you look at any particular app (lets say Words), then the way our build is configured makes it impossible to not to build the apps themselves. So, atleast for now, we need to build the full apps for Words, Sheets and Stage for CA to work properly. Maybe what we can do is that from the PA package we can remove the .desktop files for the apps or blacklist them. They are already blacklisted :) Currently it's just wasted disk space (which isn't necessarily all that abundant on a tablet) to have it all installed. ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: Packaging of Calligra for PA
First of all, a huge thanks to Friedrich for taking this up :) On Sat, Feb 9, 2013 at 12:55 AM, Thomas Pfeiffer colo...@autistici.orgwrote: On Friday 08 February 2013 16:23:26 Marco Martin wrote: On Friday 08 February 2013, Friedrich W. H. Kossebau wrote: Heya, I would like to do my little bit of contributing to PA, by the means of caring for the packaging of Calligra. Given that I meanwhile got knee-deep into Calligra code and project :) I also have an interest to make it shine as much as possible on PA. awesome, that would be very appreciated :D +1 About Calligra, at the moment it builds correctly, regarding how should be built, what version or if the package splitting could need some revision, here you probably know more ;) Is it possible to build Calligra Active without all the desktop GUIs, or have the GUIs not been separated from the engine yet? It feels weird to have a full office suite with full GUIs installed when all you want is the document viewer... Well the Calligra libs and the rendering bits like flake are separate and shared by all Calligra applications. However, when you look at any particular app (lets say Words), then the way our build is configured makes it impossible to not to build the apps themselves. So, atleast for now, we need to build the full apps for Words, Sheets and Stage for CA to work properly. Maybe what we can do is that from the PA package we can remove the .desktop files for the apps or blacklist them. Plus I think file associations need some love, currently some types of documents load in the desktop versions of Calligra applications, others do not have Calligra associated with them at all. ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active -- Shantanu Tushar(UTC +0530) http://www.shantanutushar.com ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Packaging of Calligra for PA
Heya, I would like to do my little bit of contributing to PA, by the means of caring for the packaging of Calligra. Given that I meanwhile got knee-deep into Calligra code and project :) I also have an interest to make it shine as much as possible on PA. So I would e.g. care to have the latest (now 2.6.0, not 2.6 beta1) stuff packaged and also have the CSV import filter properly installed ;) (Would for me also yield some experience how packagers experience the Calligra code dumps) Some may remember I had been involved in the community packaging of KDE software for MeeGo, so you can expect some level of experience. So how could I help with this? What wiki pages/docs can I read to prepare before I say Hi on #active during the WE? Cheers Friedrich ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: Packaging of Calligra for PA
On Friday, February 8, 2013 15:20:20 Friedrich W. H. Kossebau wrote: So how could I help with this? What wiki pages/docs can I read to prepare before I say Hi on #active during the WE? as you have experience with MeeGo packaging this should be a breeze :) Marco is our packaging coordinator at the moment, so i'd suggest coordinating with him on irc for sure. it would be *great* to have more packaging hands on board. *thanks* for getting involved! -- Aaron J. Seigo signature.asc Description: This is a digitally signed message part. ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: Packaging of Calligra for PA
On Friday 08 February 2013, Friedrich W. H. Kossebau wrote: Heya, I would like to do my little bit of contributing to PA, by the means of caring for the packaging of Calligra. Given that I meanwhile got knee-deep into Calligra code and project :) I also have an interest to make it shine as much as possible on PA. awesome, that would be very appreciated :D So I would e.g. care to have the latest (now 2.6.0, not 2.6 beta1) stuff packaged and also have the CSV import filter properly installed ;) (Would for me also yield some experience how packagers experience the Calligra code dumps) Some may remember I had been involved in the community packaging of KDE software for MeeGo, so you can expect some level of experience. yeah, remember at the berlin sprint back then ;) (btw your user still has all permissions on https://build.pub.meego.com/project/show?project=Project%3AKDE%3ADevel so all should be ready to go) About Calligra, at the moment it builds correctly, regarding how should be built, what version or if the package splitting could need some revision, here you probably know more ;) just as other information potentially useful. I think in the past some work on calligra active (either in code or packaging) has been done by Shantanu, Maurice, and iirc Leinir recently did some experients with the branch with krita sketch, so may help some coordination there as well Cheers, Marco Martin ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: Packaging of Calligra for PA
On Friday 08 February 2013 16:23:26 Marco Martin wrote: On Friday 08 February 2013, Friedrich W. H. Kossebau wrote: Heya, I would like to do my little bit of contributing to PA, by the means of caring for the packaging of Calligra. Given that I meanwhile got knee-deep into Calligra code and project :) I also have an interest to make it shine as much as possible on PA. awesome, that would be very appreciated :D +1 About Calligra, at the moment it builds correctly, regarding how should be built, what version or if the package splitting could need some revision, here you probably know more ;) Is it possible to build Calligra Active without all the desktop GUIs, or have the GUIs not been separated from the engine yet? It feels weird to have a full office suite with full GUIs installed when all you want is the document viewer... Plus I think file associations need some love, currently some types of documents load in the desktop versions of Calligra applications, others do not have Calligra associated with them at all. ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
