<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">We can have both of them. <div class=""><br class=""></div><div class="">If the author put:</div><div class="">min_version >3.2;</div><div class=""><br class=""></div><div class="">then the plugin will install BUT somebody would have added somewhere that it does not work for version 3.x.x and open an issue somewhere.</div><div class=""><br class=""></div><div class="">Denis</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 09 Mar 2015, at 10:18, <a href="mailto:jens.vieler@id.uzh.ch" class="">jens.vieler@id.uzh.ch</a> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><p class=""><font size="2" face="sans-serif" class="">Good job Ian and Denis, but am i wrong thinking this requires, that the author of the plugin is still in progress or available!? Or who may include min_/max_version to the code?</font><br class="">
<font size="2" face="sans-serif" class="">A lot of Bazaar-Plugins were touched in 2011, 2012 for the last time :-( So perhaps the author is not in touch with EP anymore - although his plugin would work for years...</font><br class="">
<br class="">
<font size="2" face="sans-serif" class="">In clear words: Who should decide? Thats what i meant with crowd-voting. This is actual feedback.</font><br class="">
<br class="">
<font size="2" face="sans-serif" class="">-- <br class="">
Jens Vieler<br class="">
Informatikdienste<br class="">
Universität Zürich<br class="">
Winterthurerstr. 190<br class="">
CH-8057 Zürich<br class="">
<br class="">
mail: <a href="mailto:jens.vieler@id.uzh.ch" class="">jens.vieler@id.uzh.ch</a><br class="">
phone: +41 44 63 56777<br class="">
<a href="http://www.id.uzh.ch/" class="">http://www.id.uzh.ch</a></font><br class="">
<br class="">
<span id="cid:1__=4EBBF490DFA1D46D8f9e8a93df9@lotus.uzh.ch"><graycol.gif></span><font size="2" color="#424282" face="sans-serif" class="">Ian Stuart ---09.03.2015 10:05:43---On 09/03/15 08:48, Denis Pitzalis wrote: > Hi all,</font><br class="">
<br class="">
<font size="1" color="#5F5F5F" face="sans-serif" class="">Von: </font><font size="1" face="sans-serif" class="">Ian Stuart <<a href="mailto:Ian.Stuart@ed.ac.uk" class="">Ian.Stuart@ed.ac.uk</a>></font><br class="">
<font size="1" color="#5F5F5F" face="sans-serif" class="">An: </font><font size="1" face="sans-serif" class=""><a href="mailto:eprints-tech@ecs.soton.ac.uk" class="">eprints-tech@ecs.soton.ac.uk</a></font><br class="">
<font size="1" color="#5F5F5F" face="sans-serif" class="">Datum: </font><font size="1" face="sans-serif" class="">09.03.2015 10:05</font><br class="">
<font size="1" color="#5F5F5F" face="sans-serif" class="">Betreff: </font><font size="1" face="sans-serif" class="">[EP-tech] Re: Bazaar-Plugins vs. New EPrint Versions</font><br class="">
<font size="1" color="#5F5F5F" face="sans-serif" class="">Gesendet von: </font><font size="1" face="sans-serif" class=""><a href="mailto:eprints-tech-bounces@ecs.soton.ac.uk" class="">eprints-tech-bounces@ecs.soton.ac.uk</a></font><br class="">
</p><hr width="100%" size="2" align="left" noshade="" style="color:#8091A5; " class=""><br class="">
<br class="">
<br class="">
<tt class=""><font size="2" class="">On 09/03/15 08:48, Denis Pitzalis wrote:<br class="">
> Hi all,<br class="">
><br class="">
> Maybe even easier would be to add a min_version and a max_version<br class="">
> variables in the plugin definition. Like in PHP CMS. So we can define:<br class="">
> $self->{min_version} = “>= 3.3.10”;<br class="">
> $self->{max_version} = “< 3.3.12”;<br class="">
><br class="">
> so we are sure that we always install the good version of a plugin.<br class="">
><br class="">
> We could even go further and add a dependencies like:<br class="">
> $self->{dependency} = “icon-builder>1.1.4”;<br class="">
><br class="">
> etc<br class="">
><br class="">
> What do you think?<br class="">
<br class="">
The downside to this approach is that plugins should remain compatible <br class="">
with all releases of EPrints (and certainly within a Version: 3.1; 3.2; <br class="">
3.3;...)<br class="">
The changes that kill plugins are changes to API calls... and those <br class="">
shouldn't change within a version (so all function/api calls in 3.3.1 <br class="">
should still work in 3.3.14 - though there may be additional <br class="">
functionality available within those calls, or via new calls)<br class="">
<br class="">
I'd be happy with<br class="">
<br class="">
$self->{min_version} = “>= 3.2”;<br class="">
$self->{max_version} = “< 3.4”;<br class="">
<br class="">
Anything else, and all Bazaar plugins automatically go "out of scope" on <br class="">
every new release, until they are tested against an install of that new <br class="">
release.<br class="">
<br class="">
-- <br class="">
<br class="">
Ian Stuart.<br class="">
Developer: ORI, RJ-Broker, and <a href="http://OpenDepot.org" class="">OpenDepot.org</a><br class="">
Bibliographics and Multimedia Service Delivery team,<br class="">
EDINA,<br class="">
The University of Edinburgh.<br class="">
<br class="">
</font></tt><tt class=""><font size="2" class=""><a href="http://edina.ac.uk/" class="">http://edina.ac.uk/</a></font></tt><tt class=""><font size="2" class=""><br class="">
<br class="">
This email was sent via the University of Edinburgh.<br class="">
<br class="">
The University of Edinburgh is a charitable body, registered in<br class="">
Scotland, with registration number SC005336.<br class="">
<br class="">
<br class="">
*** Options: </font></tt><tt class=""><font size="2" class=""><a href="http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech" class="">http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech</a></font></tt><tt class=""><font size="2" class=""><br class="">
*** Archive: </font></tt><tt class=""><font size="2" class=""><a href="http://www.eprints.org/tech.php/" class="">http://www.eprints.org/tech.php/</a></font></tt><tt class=""><font size="2" class=""><br class="">
*** EPrints community wiki: </font></tt><tt class=""><font size="2" class=""><a href="http://wiki.eprints.org/" class="">http://wiki.eprints.org/</a></font></tt><tt class=""><font size="2" class=""><br class="">
*** EPrints developers Forum: </font></tt><tt class=""><font size="2" class=""><a href="http://forum.eprints.org/" class="">http://forum.eprints.org/</a></font></tt><tt class=""><font size="2" class=""><br class="">
</font></tt><br class="">
</div>*** Options: <a href="http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech" class="">http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech</a><br class="">*** Archive: <a href="http://www.eprints.org/tech.php/" class="">http://www.eprints.org/tech.php/</a><br class="">*** EPrints community wiki: <a href="http://wiki.eprints.org/" class="">http://wiki.eprints.org/</a><br class="">*** EPrints developers Forum: <a href="http://forum.eprints.org/" class="">http://forum.eprints.org/</a><br class=""></div></blockquote></div><br class=""></div></body></html>