Packaging up a custom release

[mwillis]

I'm currently working on modifying OJS to suit my clients additional requirements, however I want to make sure that I can keep up to date with new versions release for the OJS product.

My current solution would be to check out OJS from CVS and develop locally. If a new version is released then update using the cvs update -r <TAG> command and merge the changes appropriately.

Once my changes have been made I would like to package up my customised version (e.g. into a tar.gz file) ready to load on to the production web site. This packaged version would only contain the core OJS files (i.e. no ftp upload files, etc) so it would not over-write any site specific information once "un-tared". Is there a script to so this at the moment or am I better off writing one to tar them up myself?

Thanks in advance.

[asmecher]

Hi mwillis,

Use the tools/buildpkg.sh script to build a tarball; it's written to build against a CVS repository, so be sure to customize it with your own repository as necessary.

If you think your additions might be useful to the OJS community at large, consider contributing them back to us here -- if we include some of them in the core OJS distribution, you'll be less likely to run into maintenance problems in the future.

Regards,
Alec Smecher
Open Journal Systems Team

[mwillis]

Thanks for the information, since the buildpkg.sh script will only build from CVS version it might be nice to customise it to build a package against the current locally copy of the OJS project (i.e. without pulling the data from CVS).

I'm having a look at doing this at the moment. If anyone feels that this is useful feature then I could look at submitting this back to the project for review.

Thanks