EPrints Technical Mailing List Archive

See the EPrints wiki for instructions on how to join this mailing list and related information.

Message: #03431

< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First

[EP-tech] Re: Managing Bazaar package development

I used that (the tool) a long time ago now, and I can’t remember if I ever got it working right.   I suppose it depends what you are working on how you’d symlink it. I’ve been working on a theme package so it’s all nicely contained in one folder, so easy to link.

 

David

 

From: eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk] On Behalf Of Mark Gregson
Sent: 03 September 2014 01:14
To: eprints-tech@ecs.soton.ac.uk
Subject: [EP-tech] Re: Managing Bazaar package development

 

Thanks David. The git sub-module method seems clean and efficient.

 

For the symlink option, are you manually linking each file, or is this what tools/epm link_cfg|link_lib does?

 

Cheers

Mark

 

From: eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk] On Behalf Of David McElroy
Sent: Tuesday, 2 September 2014 11:21 PM
To: eprints-tech@ecs.soton.ac.uk
Subject: [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.

 

David

 

From: eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk] On Behalf Of Mark Gregson
Sent: 02 September 2014 13:49
To: eprints-tech@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.

 

Cheers

Mark

 

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/
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



This email has been scanned for email related threats and delivered safely by Mimecast.
For more information please visit http://www.mimecast.com