Before anything else — Please forgive me, I'm in a hurry and must go in ≤10 min So I'll be brief, and will comment later on.
I have created a Debian package for OJS (see my blog post on the subject, http://gwolf.org/blog/packaging-pkp-oks ... als-system ). I am a Debian Developer, and so far, from the packaging side, it is mostly done. It does address several of the points brought up in this thread, as far as I read it (less than half FWIW). I have talked over with Jerico, and he explained to me I probably should not be using the system copy of ADODB but the modified one - Ok, I'll check that soon (as soon as I have the Bugzilla account).
I have uploaded my packaging as a different branch to the SVN repository. Silly me, I didn't check our WNPP pages for OJS (http://bugs.debian.org/wnpp), where your intentions were already registered (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=511879). Jerico and I are, happily, more than happy to collaborate!
I uploaded my work to the gwolf branch of your repository, you can browse it at:
http://svn.debian.org/wsvn/collab-maint ... lf_debian_
Anyway — The main packaging differences I can think of right away are:
- I used DebHelper 7 as a packaging framework, it is more widely accepted nowadays in Debian than CDBS, and AFAICT it is greatly more readable. Of course, it is just an opinion.
- I am using the 3.0 (quilt) source format (http://wiki.debian.org/Projects/DebSrc3.0), which implies the Quilt dependency and makes workflow a bit easier
- I have not yet looked at your debian/patches directory. Besides that, everything should be equivalent to what you have done.
- I did add a patch, which I would appreciate you looked at. Of course, this might be an ADODB issue (among the little details Jerico told me you had patched on it): http://svn.debian.org/wsvn/collab-maint ... _undefined
- debian/watch cannot be reliably used, as it would pull the development (2.3.x) releases. We can later see how this can be solved. Should not be a showstopper, FWIW
- Some directories are a bit different. Should not hurt... I guess
- I do not think we should be performing all that level of configuration from Debconf. OJS is quite auto-installable via its own interface, and explains failures in a very good, predictable way. I am leaving the application ready to be configured by Web. We can talk this over, of course (even better, you have already done the work for it )
- Several minor, stylistic packaging subtleties... which do not impact the end product but the process
That's it for today. Hope to work with you for the future!