openshot.developers team mailing list archive
-
openshot.developers team
-
Mailing list archive
-
Message #00140
Copyrights, file organisation
In producing the Debian packaging I need to ensure that I list all the
copyright holders.
A simple grep only shows me Jonathan Thomas but from what I understand
about the documentation and translations there should be others.
Would it be possible to maintain a ./CREDITS file for this purpose?
>From that I can ensure the Debian packaging is correct and monitor it
for changes.
Secondly, I'm wondering about the file/directory layout of the project.
There's only a couple of files in the root (.project, .pydevproject). It
would be better if the project package documentation (README, COPYING,
CREDITS, NEWS, etc., were in the root rather than in ./main/ - is there
a reason for the current layout?
I'll probably have one or two other questions as I delve deeper into the
actual source, some of which may appear naive, but bare with me because
it is always better to spell things out rather than rely on differing
assumptions.
I've packaged and published (to my video-editors PPA) the latest frei0r
and libx264 packages this morning. Together with the ffmpeg and MLT
packages already there they should complete all the dependencies
required.
https://launchpad.net/~intuitivenipple/+archive/video-editors
It'll take me a little while to be sure I've covered all the bases with
the openshot package itself since it is the first pure-Python
(interpreted not compiled) package I've done and has quite different
workflow than a regular autogen/autoconf/configure/make binary project.
I'm working from the latest bzr so the first package will be:
openshot (0.9.24-0ubuntu1) for jaunty and karmic.
Once this is done we may need to think about the best approach for
moving openshot to the project's own PPA. The primary issue I see is the
duplication of the dependency packages.
For example both kdenlive and openshot will depend on the same packages
(ffmpeg, MLT, frei0r, etc.) but at present each project will duplicate
the packages in their respective archives.
This will lead to version conflicts for users who attempt to install
both editors and potentially one editor being broken if functionality it
expects to find in dependencies isn't there or as expected.
It is a shame Karmic isn't more current on these supporting packages but
as Feature Freeze is on Thursday I doubt the package maintainers would
have the time to refresh those packages in the Ubuntu archives.
Follow ups