openshot.developers team mailing list archive
-
openshot.developers team
-
Mailing list archive
-
Message #00149
Re: Packaging related questions
TJ, I have included my answers below.
Thanks,
-Jonathan
On Tue, Aug 25, 2009 at 9:56 AM, TJ <ubuntu@xxxxxxxxxxx> wrote:
> These are the questions that have cropped up so far:
>
> 1. What version(s) of Python are required (i.e; >= 2.2, >=2.4) ?
I've only tested on Python 2.5 and greater. It might work with older
> version too, but that's a bit of an unknown.
>
>
> 2. install/postinst.py is trying to copy MLT python bindings (mlt.py,
> _mlt.so, mlt_wrap.o) which don't exist (at least the source doesn't) -
> are these no longer required?
These 3 files are installed by my custom MLT .deb installer. After building
> MLT, I ran the following commands to generate the swig Python bindings:
>
> $ cd ~/mlt/src/swig/python
> $ sudo bash build
>
Then these 3 files need to be copied into the Python path (i.e. the
> site-packages or dist-packages folders, or any other folder in the Python
> path). Ideally, the MLT Python bindings would be packaged separately (i.e.
> something like mlt-python-bindings, or what ever). If done correctly, you
> can open up the Python shell, and type "import mlt", and it will not throw
> an error. This has always been one of the more difficult steps to
> automate in my build wizard and in the packaging I've attempted so far. =)
>
>
> 3. install/openshot.dpm isn't installed - should it be, or is it not
> required?
This file can be ignored. I'm going to delete it from the trunk.
>
>
> 4. install/openshot.dpm doesn't seem to be viewable according to its
> mime-type (TrueType font application/x-font-ttf), what type is it?
>
> 5. install/openshot.desktop contains absolute paths for icons
> to /usr/local/share/* locations which need to be become agnostic. The
> icon should be installed in the system icons directory. If the logo icon
> is referenced from the program code that will need updating to detect
> the system path location and concatenate it with the filename.
This is the only path in OpenShot that is hard-coded. Everywhere inside
> OpenShot we do exactly like you suggest, and concatenate the system path
> with the filename. I just didn't know where to install this icon, and how
> to refer to it's path on the .desktop file.
>
>
> 6. Two directories (thumbnail/ and queue/) appear to be per-user
> 'runtime' rather than 'build-time' requirements. This suggests they
> should be created in the user's home directory: ~/.openshot/thumbnail/
> and ~/.openshot/queue/.
> The primary reason for this would be user permissions to the
> applications' installation directory are restricted to read+execute.
> This requires programs changes so we'll need to liaise on this since the
> program would need to ensure the directories are created at each launch
> - the Debian package wouldn't have anything to do with them.
> I will go ahead and move these folders into the home directory. This
> should be a fairly easy change. OpenShot will create these folders at
> runtime, so there shouldn't be any problems.
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openshot.developers<https://launchpad.net/%7Eopenshot.developers>
> Post to : openshot.developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openshot.developers<https://launchpad.net/%7Eopenshot.developers>
> More help : https://help.launchpad.net/ListHelp
>
Follow ups
References