OJS OCS OMP OHS

You are viewing the PKP Support Forum | PKP Home Wiki



Packaging up a custom release

OJS development discussion, enhancement requests, third-party patches and plug-ins.

Moderators: jmacgreg, btbell, michael, bdgregg, barbarah, asmecher

Forum rules
Developer Resources:

Documentation: The OJS Technical Reference and the OJS API Reference are both available from the OJS Documentation page.

Git: You can access our public Git Repository here. Comprehensive Git usage instructions are available on the wiki.

Bugzilla: You can access our Bugzilla report tracker here.

Search: You can use our Google Custom Search to search across our main website, the support forum, and Bugzilla.

Questions and discussion are welcome, but if you have a workflow or usability question you should probably post to the OJS Editorial Support and Discussion subforum; if you have a technical support question, try the OJS Technical Support subforum.

Packaging up a custom release

Postby mwillis » Mon Aug 21, 2006 8:16 am

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.
mwillis
 
Posts: 2
Joined: Mon Aug 21, 2006 7:12 am

Postby asmecher » Wed Aug 23, 2006 6:00 am

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
asmecher
 
Posts: 9082
Joined: Wed Aug 10, 2005 12:56 pm

buildpkg.sh script

Postby mwillis » Wed Aug 23, 2006 6:08 am

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
mwillis
 
Posts: 2
Joined: Mon Aug 21, 2006 7:12 am


Return to OJS Development

Who is online

Users browsing this forum: No registered users and 1 guest