[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[EP-tech] Re: Managing Bazaar package development

I've used a couple of methods now.

1.       Develop the plugin in a separate decretory somewhere else on the some machine (/home/david/dev/bazaar-package) and then link it back to where it should be in the eprints archive dir.

2.       Same as above, but instead of linking, create submodule in your eprints git repo, and pull it in when you do some development on your plugin code.


From: eprints-tech-bounces at ecs.soton.ac.uk [mailto:eprints-tech-bounces at ecs.soton.ac.uk] On Behalf Of Mark Gregson
Sent: 02 September 2014 13:49
To: eprints-tech at ecs.soton.ac.uk
Subject: [EP-tech] Managing Bazaar package development

Hi Bazaar package developers

I'm just starting to work with Bazaar packages and I'm wondering how to handle their development, packaging and upload. The key issue is that I want to manage the source code for the package in a separate git repo to my EPrints core but developing the code in an EPrints install and then copying the code back to a git repo to commit seems somewhat clumsy. I'm tempted to write a script for packaging and installing an EPM from a git working copy (as far as I can see tools/epm doesn't really help with this, or am I missing something?).

I'd be very interested to hear how you more experienced package developers are handling this.


Mark Gregson | Applications and Development Team Leader
Library eServices | Queensland University of Technology
Level 3 | R Block | Kelvin Grove Campus | GPO Box 2434 | Brisbane 4001
Phone: +61 7 3138 3782 | Web: http://eprints.qut.edu.au/<http://www.qut.edu.au/>
ABN: 83 791 724 622
CRICOS No: 00213J
 This email has been scanned for email related threats and delivered safely by Mimecast.
 For more information please visit http://www.mimecast.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ecs.soton.ac.uk/pipermail/eprints-tech/attachments/20140902/8a69595c/attachment.html