Hi Thomas,
Martin did quite some work on packaging PISI and its deps. (see attached
email) ...
I think, all the deps are in there now; haven't yet had the time to test
everything ...
>From my point of view, there is still a need to create proper BB-File
for PISI - see discussion in second attached email.
If you have dealt with these things before - what is your opinion about it??
Greetings
Michael
Thomas Zimmermann wrote:
> Am Sonntag 16 August 2009 22:17:43 schrieb Michael Pilgermann:
>> Dear all,
>>
>> For an Openmoko PIM Synchronization tool (called PISI) I developed a
>> module to integrate with SyncML-servers this weekend. It is all running
>> fine on my Linux box (desktop) already.
>>
>> I had some libs to install in order to get prepared. Now, for putting
>> the package together for the Openmoko I need to port them. However, I am
>> not very familar with this stuff (Python programmer) and have no
>> toolchain installed (I think, I heart that's the way to go for that kind
>> of stuff) ...
>>
>>
>> So my question is, whether somebody (who has maybe already a fully
>> functional toolchain installed) could assemble Openmoko packages (best
>> ipk I would say) for the following three modules:
>>
>> - wbxml
>> (http://sourceforge.net/projects/libwbxml/files/libwbxml/0.10.7/libwbxml-0.
>> 10.7.tar.gz/download) - libsoup (http://live.gnome.org/LibSoup)
>> - libsyncml
>> (http://sourceforge.net/projects/libsyncml/files/libsyncml/0.5.4/libsyncml-
>> 0.5.4.tar.gz/download)
>>
>>
>> Uploading them to opkg.org would be grant - but if you just send them
>> over, I would do the rest, too ...
>>
>> Please, please help - if I need to do it myself, it will probably take
>> me ages (and will look like the openldap module ;))
>>
>> Michael
>
> Did you find someone who would help you? If not i will do it.
>
> Thomas
> _______________________________________________
> Shr-User mailing list
> [email protected]
> http://lists.shr-project.org/mailman/listinfo/shr-user
--- Begin Message ---
Hi,
on Friday I uploaded patch for OE repository to shr trac:
http://trac.shr-project.org/trac/ticket/592
<http://trac.shr-project.org/trac/ticket/592>Patch contains support for
setuptools (http://pypi.python.org/pypi/setuptools), which seems like
standard tool for managing python packages, that's files ez_setup.py,
setup.py and setup.cfg. It would be nice if you include those 3 files in
your source distribution package.
I also found few files missing from
http://projects.openmoko.org/frs/download.php/888/pisi-src-0.4.4.tar.gz,
which were available in subversion repository, so I made only bbfile for
"live" subversion version of pisi, I can found which files were missing if
you can include them to pisi-src too.
As last modification of your source distribution I created pisi python
module and moved all pisi stuff and subdirs there, because this bbfile
installs pisi directly in /usr/lib/python*/site-packages/pisi not to
/opt/pisi and having lots of files and directories only for pisi directly in
site-packages seemed wrong for me.
So i rearranged source files like this:
mkdir pisi
mv pisi*.py pisi
touch pisi/__init__.py
mv contacts/ modules/ events/ tests/ thirdparty/ pisi
As I said before, I'm not python programer so setuptools and python packages
are new for me, so it would be nice if someone could confirm, that this
structure is sane and you could rearrange files in subversion to simplyfi
building process.
I'll try to prepare bbfiles for new development version dependencies as you
wrote in second thread.
JaMa
On Fri, Aug 14, 2009 at 7:35 PM, Michael Pilgermann <[email protected]>wrote:
> JaMa,
>
> thx for this offer. I don't really know, what in detail you are talking
> about ... i was quite happy, that I managed to assemble ipkg - this is
> all done automatically using a Makefile:
>
> https://projects.openmoko.org/plugins/scmsvn/viewcvs.php/*checkout*/trunk/Makefile?rev=135&root=pisi
>
> But integrating all this in feeds of repositories of course sounds good
> to me ... just let me know, what exactly I can do for you - I am sure we
> can sort that out ....
>
> (till now I have always just copied the files into my ipkgs)
>
> Michael
>
>
> Martin Jansa wrote:
> >
> >
> > On Thu, Aug 13, 2009 at 11:49 AM, Martin Jansa <[email protected]
> > <mailto:[email protected]>> wrote:
> >
> > I have no experience with python, but I can try to prepare setup.py
> for
> > setuptools next week, if you have no time or interest in it and then
> > send you patch.
> >
> >
> > I had some spare time.. so before going for vacation, here is something
> > which works for me, at least seems like working for me :).
> >
> > Maybe something could be integrated upstream so simplify bbfile for next
> > version.
> >
> > Regards,
> >
> > JaMa
> >
> >
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > Openmoko community mailing list
> > [email protected]
> > http://lists.openmoko.org/mailman/listinfo/community
>
>
> _______________________________________________
> Openmoko community mailing list
> [email protected]
> http://lists.openmoko.org/mailman/listinfo/community
>
_______________________________________________
Openmoko community mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/community
--- End Message ---
--- Begin Message ---
>
> *** Should we really install a Python application as a site-package?? ***
>
> Setuptools (and whatever similar stuff is out there for Python packaging)
> is a very good tool to assemble and distribute Python site-packages (so to
> say Python libraries) - stuff, that extends Python by some additional
> functionality. A program, however, does not extend the functionaility of
> the language - it is just an application itself.
I agree, installing applications in site-packages just feels *wrong*. That
being said, A number of applications still do it. :(
Im not sure, but perhaps setuptools, can be told to install to an alternative
location?
Adolph
_______________________________________________
Openmoko community mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/community
--- End Message ---
_______________________________________________
Openmoko community mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/community
