[Debian-ezgo-packaging] Debian packaging

[Franklin Weng]

Hi all,

Thanks for all your suggestions and advises.  Since Andreas strongly
suggested me to be familiar with debian packaging first, I spent a week and
did some work.  Please visit

ftp://goodhorse.idv.tw/debian-ezgo/

I read and studied some debian packaging documents [1][2][3] and made three
packages: ezgo-artwork, ezgo-menu and ezgo-opencontent.  When I install
these three packages on a debian-edu (skolelinux) system it can become ezgo
style successfully, and when I remove or purge them it can revert back to
the original settings (except one thing -- see below.)

For ezgo-artwork, I studied and referenced debian-edu-artwork about how to
replace kdm / ksplash and desktop background images, and followed the
example of debian packaging introduction [1].  I also followed
debian-edu-artwork and changed some settings under debian/.  However, I
have to admit that I don't really understand some settings in
debian-edu-artwork.  Like debian-edu-artwork.install，I don't understand why
they put

debian/tmp/etc
debian/tmp/usr/share

I just followed their example, and it worked!  Besides, I only put settings
with KDE only.

For ezgo-menu, it has a "dirty hacked" component, about changing the
content of application desktop files.  This step is to change the name
(mainly for traditional Chinese) into CATEGORY_NAME form.  However, it is
not revertible.  I mean, if I changed it, it would not be able to revert to
their original setting after I purge the ezgo-menu package.

For ezgo-opencontent, currently only PhET is inside.  I put a binary tar gz
file and extract it when installing.  The problem of this package is that
it depends on browser's java plugins.  Right now I know that it should work
for all simulations using Oracle Java 8.  However it didn't work using
current icetea java in debian-edu original system.  I don't know what's
debian's policy about java.

In all these packages, the settings under debian/ are still not complete,
and still have many defects hence not debian acceptable.  Anyway, now I can
demo this system to our local teachers.  My short term target is reached.

It's just a start.  The next step I want to study is how to turn this into
"Pure" (debian acceptable) debian packages.

Therefore, if you have time, please have a look at these packages and I
need your advises about
 - debian packaging : how should I improve the debian packaging?
 - how to solve the "unrevertible" problem of ezgo-menu?

And the long term target:  to make a debian-ezgo pure blends.

Any advice and help will be very appreciated.



Franklin

[1] https://wiki.debian.org/IntroDebianPackaging
[2] https://wiki.debian.org/HowToPackageForDebian
[3] packaging-tutorial packages
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/debian-ezgo-packaging/attachments/20140314/c13f2c7c/attachment.html>