Re: [SailfishDevel] prefered way to build rpm package for a project written in python/pyotherside?
well, i dont know other way than rpmbuild :) On 06.03.2014 03:13, Boris Pohler wrote: Hi, I wrote my first little program using python/pyotherside. I develop directly on the jolla-device (no sdk) and would like to build a rpm package to distribute to openrepos (and later to harbour, if python is accepted). What is the prefered (easiest) way? Boris P.S.: My desktop-distribution is Archlinux. ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] prefered way to build rpm package for a project written in python/pyotherside?
I've never built packages on the Jolla device if that's what you mean but this is what you do on the SDK: 1. Install Virtualbox. 2. Install Sailfish SDK. 3. Start Virtualbox and run the MerSDK image. 4. Log in with SSH. (ssh -p -i ~/SailfishOS/vmshare/ssh/private_keys/engine/mersdk mersdk@localhost) 5. Build packages using the sb2 and rpmbuild commands. You can set your default build target in: [xerxes2@ninja ~]$ cat .scratchbox2/config DEFAULT_TARGET=SailfishOS-armv7hl You may run into some problems with building python packages as user, problems are fixable, but you can build as root too (-R). Greets Jens On Wed, Mar 5, 2014 at 10:13 PM, Boris Pohler bo...@pohlers-web.de wrote: Hi, I wrote my first little program using python/pyotherside. I develop directly on the jolla-device (no sdk) and would like to build a rpm package to distribute to openrepos (and later to harbour, if python is accepted). What is the prefered (easiest) way? Boris P.S.: My desktop-distribution is Archlinux. ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] prefered way to build rpm package for a project written in python/pyotherside?
5.3.2014 22:13, Boris Pohler: Hi, I wrote my first little program using python/pyotherside. I develop directly on the jolla-device (no sdk) and would like to build a rpm package to distribute to openrepos (and later to harbour, if python is accepted). What is the prefered (easiest) way? Well, I'm for example using OBS to build packages for my Python/PyOtherSide based modRana application (the modRana package available from OpenRepos since last week[2] was build on the Mer OBS) and the other possibility is the already mentioned rmbuild utility. Both boil down to basically one thing - you need source code archive (tarball) and metadata file (spec file). For example, this is[3] my tarball the (rather crazy) specfile for building the modRana package. As you can see, the specfile just has some metadata like application author name, version, names of dependencies and listing of files and where they should end. So basically what you can do is take a specfile (the modRana one or some less crazy one), modify it to describe your application and use it to build your own packages with OBS or the rpmbuild utility. With best wishes Martin Kolman PS.: Official documentation/support for building Python applications for Sailfish would still be welcome. :) [1] https://build.merproject.org/package/show?package=harbour-modranaproject=home%3AMartinK%3Asailfish%3Amodrana [2] https://openrepos.net/content/martink/modrana-0 [3] https://build.merproject.org/package/files?package=harbour-modranaproject=home%3AMartinK%3Asailfish%3Amodrana Boris P.S.: My desktop-distribution is Archlinux. ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] prefered way to build rpm package for a project written in python/pyotherside?
05.03.2014 23:13, Boris Pohler wrote: I wrote my first little program using python/pyotherside. I develop directly on the jolla-device (no sdk) and would like to build a rpm package to distribute to openrepos (and later to harbour, if python is accepted). What is the prefered (easiest) way? If it's pure Python and QML, the package will be noarch and you can build the RPM on any system, e.g. your desktop system. You just need a spec file and then run rpmbuild. I build helsinki-transit-live packages myself on a Debian desktop system. I have split the file copying to a Makefile and the spec file just calls make install (but you can just as well put the copy commands in the spec file if that's easier). If building on a non-RPM system, you can use rpmbuild --nodeps to avoid stopping at checking BuildRequires. https://github.com/otsaloma/helsinki-transit-live (see RELEASING, Makefile and rpm/*.spec) -- Osmo Salomaa otsal...@iki.fi ___ SailfishOS.org Devel mailing list
