Packaging of Calligra for PA

[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}lib<anything>.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