Hi Alessandro and others,<div><br></div><div>I think that splitting ZOO into multiple packages must make sense for a user, for example when someone only wants to install the basics on a production server.</div><div><br></div>
<div>But it should be already clear from the configure - make - install process. So if you build several packages "zoo-kernel", "zoo-services" and "zoo-api" for example and you have to write custom scripts to pick one part from here and one from there, this wouldn't be a good idea IMO. </div>
<div>So if ZOO-Project is already designed that it wants to make certain parts optional (or will do in the future), then it makes sense to split packages, otherwise not.</div><div><br></div><div>Daniel</div><div><br></div>
<div>PS: I would prefer some anming like zoo-<name>-x.x.x if this is not against some naming convention</div><div><br></div><div><br><br><div class="gmail_quote">
2010/9/21 Alessandro Frigeri <span dir="ltr"><<a href="mailto:alessandro.frigeri@gmail.com" target="_blank">alessandro.frigeri@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<br>
thanks for all the suggestions. Yesterday I've worked at a simple<br>
version of the package that will carry zoo_loader.cgi in the cgi-bin<br>
dir and main.cfg in the examples directory, plus all the standard<br>
debian files. The good thing is that the packaging build process<br>
seems to work quite well, and that's good for porting it to different<br>
architectures.<br>
<br>
For the name of the package, from the discussion it seems that we have<br>
to chose from two options:<br>
<br>
zoowps-x.x.x - this is the case if zoo will always talk 'wps'<br>
<br>
zookernel-x.x.x - if 'wps' is just one of the 'languages' zoo will<br>
talk with clients in future (as I understood from Venka's message),<br>
and the 'kernel' is to be considered the engine where to attach<br>
services communicating with 'languages' other than wps (are there<br>
other ones around yet?).<br>
<br>
Regarding the future addons, debian/ubunt provides the<br>
"packagename-extras" naming scheme option that fits well with our case<br>
for extra backends.<br>
<br>
I don't want to be too pedant on this, since it is only a name, but<br>
choosing a good package name will save time later on.<br>
<br>
Alessandro<br>
<br>
<br>
2010/9/21 Venkatesh Raghavan <<a href="mailto:raghavan@media.osaka-cu.ac.jp" target="_blank">raghavan@media.osaka-cu.ac.jp</a>>:<br>
<div><div></div><div>> Someday ZOO could hopefully be more than WPS<br>
> only.<br>
><br>
> My suggestion would be to name the package as<br>
> zoo-kernel with subsequent release zoo-services<br>
> and zoo-api.<br>
><br>
> Since multi-language support is one of the<br>
> main features of the ZOO-Kernel, the present release<br>
> (ZOO-Kernel-1.0.1) could C/C++, Fortran and Python<br>
> support. Future stable release (ZOO-Kernel-1.2.X) could<br>
> include support for javascript and other newly<br>
> supported languages.<br>
><br>
> ZOO-Services and ZOO-API could be released as independent<br>
> packages.<br>
><br>
> Also a possibility of releasing ZOO-Bundle (which includes<br>
> ZOO-Kernel, ZOO-Services and ZOO-API) in the future.<br>
><br>
> Best<br>
><br>
> Venka<br>
><br>
> On 2010/09/20 22:15, Gérald Fenoy wrote:<br>
>> Hi Daniel, yes you're right, maybe better to keep WPS in the package<br>
>> name.<br>
>><br>
>> I agree also that the zoo-service and zoo-api can be installed as<br>
>> independent packages. But if we use it this way, then how can we<br>
>> provide the ZOO Kernel ? I mean that the compilation process of the<br>
>> ZOO Kernel imply that each requested Languages support have to be<br>
>> compiled at the same time. Or do we need to plan to provide multiple<br>
>> "zoo-wps" packages for each support ? I mean something like :<br>
>> zoo-wps-std for ZOO Kernel with C/C++, Fortran and Python support,<br>
>> then zoo-wps-javascript for another one including the later and with<br>
>> the javascript addition and so on ?<br>
>><br>
>> I don't know how to do this in an efficient way.<br>
>><br>
>> Let me know what you think, Regards,<br>
>><br>
>> Le 20 sept. 2010 à 14:39, Daniel Kastl a écrit :<br>
>><br>
>>> Hi Gerald,<br>
>>><br>
>>> Is ZOO-Project going to be more than WPS? Alessandro's proposal<br>
>>> idea to call it "zoo-wps" isn't bad IMO. Another idea would be - in<br>
>>> case ZOO Services and API could be installed extra - to split them<br>
>>> in packages like "zoo-kernel", "zoo-services", "zoo-api" with being<br>
>>> "zoo-kernel" required for others.<br>
>>><br>
>>> Well, shouldn't become to complicated on the other hand.<br>
>>><br>
>>> Daniel<br>
>>><br>
>>><br>
>>><br>
>>> 2010/9/20 Gérald Fenoy<<a href="mailto:gerald.fenoy@geolabs.fr" target="_blank">gerald.fenoy@geolabs.fr</a>> Hi Alessandro, nice<br>
>>> to hear from you.<br>
>>><br>
>>> I think it can be better to use ZOO-Project, if this is acceptable<br>
>>> in Debian packaging name. If not then maybe you can use<br>
>>> zoo-project.<br>
>>><br>
>>> We will create a branch and tag officially in some days, we need to<br>
>>> finalize the Perl support integration first. It was currently<br>
>>> tested by David Saggiorato on his own (some part was already<br>
>>> integrated in the SVN source tree). We also need to add a ZOO<br>
>>> Service Provider which will access some shared memory to get<br>
>>> information on the current status of a process. I think that those<br>
>>> two enhancement can be finalized really soon and then we can tag as<br>
>>> 1.0.1 version. Other plan for the 2.0 version will start next week,<br>
>>> it will include the modification of service functions signature,<br>
>>> the main reason for creating a new version.<br>
>>><br>
>>> Please use the SVN source tree and not the archive 1.0 you talked<br>
>>> about, indeed we have to provide the new version of the archive<br>
>>> soon for the new version present in SVN.<br>
>>><br>
>>> If you need the branch quickly please let me know, we will create<br>
>>> it faster than we planned to do.<br>
>>><br>
>>> Hope to hear from you, best regards,<br>
>>><br>
>>><br>
>>> Le 20 sept. 2010 à 13:22, Alessandro Frigeri a écrit :<br>
>>><br>
>>>> Hei Nick, Venka + zooers,<br>
>>>><br>
>>>> thanks for the details. Sorry, I've missed the 1.0 was there<br>
>>>> already there,<br>
>>>> <a href="http://www.zoo-project.org/dl/ZOO-Kernel-1.0.tar.bz2" target="_blank">http://www.zoo-project.org/dl/ZOO-Kernel-1.0.tar.bz2</a>, i'll submit<br>
>>>> un update to our request to debian.<br>
>>>><br>
>>>> Also, I've found there is already a package named "zoo", to<br>
>>>> manipulate zoo archives. So we can go with with "zoowps"<br>
>>>> "zoo-wps" or whatever is good to differentiate from the other<br>
>>>> package. Suggestions are welcome so we can start up in good<br>
>>>> shape with debian and the ubuntu packages.<br>
>>>><br>
>>>> For the version scheme, it seems ok to me. Nick, let's<br>
>>>> experiment an svn copy trunk to some 1.0.x tag.<br>
>>>><br>
>>>> Alessandro<br>
>>>><br>
>>>><br>
>>>> 2010/9/20 Venkatesh Raghavan<<a href="mailto:raghavan@media.osaka-cu.ac.jp" target="_blank">raghavan@media.osaka-cu.ac.jp</a>>:<br>
>>>>> Hi Alessandro,<br>
>>>>><br>
>>>>> Thanks for the follow-up at debian/ubuntu miniconf regarding<br>
>>>>> ZOO<br>
>>>>><br>
>>>>> I think ZOO could follow the similar scheme as GRASS GIS as<br>
>>>>> below;<br>
>>>>><br>
>>>>> Version number scheme:<br>
>>>>><br>
>>>>> * first number: major release number * secondary number: minor<br>
>>>>> release number (stable/development indicator) * third number:<br>
>>>>> revision<br>
>>>>><br>
>>>>> Scheme for ZOO-Kernel 1.0.1 which is presently available would<br>
>>>>> be as follows<br>
>>>>><br>
>>>>> a) 1 being the major release number b) 0 being the minor<br>
>>>>> release number c) 1 being the revision<br>
>>>>><br>
>>>>> Any suggestions from others?<br>
>>>>><br>
>>>>> Best<br>
>>>>><br>
>>>>> Venka<br>
>>>>><br>
>>>>> On 2010/09/20 6:00, nicolas bozon wrote:<br>
>>>>>> Hi Alessandro,<br>
>>>>>><br>
>>>>>> Thanks for the request to Debian ! ZOO Kernel was released on<br>
>>>>>> April 2010 under 1.0 version. We are now under the 1.0.1<br>
>>>>>> since last week, as the svn was updated with new version by<br>
>>>>>> gerald I think we still have to improve the branching, you're<br>
>>>>>> right. Best,<br>
>>>>>><br>
>>>>>> Nick<br>
>>>>>><br>
>>>>>><br>
>>>>>> 2010/9/19 Alessandro Frigeri<<a href="mailto:afrigeri@unipg.it" target="_blank">afrigeri@unipg.it</a>><br>
>>>>>><br>
>>>>>>> Hi zooers,<br>
>>>>>>><br>
>>>>>>> The debian/ubuntu mini conf was very fruitful - nice ideas<br>
>>>>>>> and nice people. For zoo, I've placed a request on<br>
>>>>>>> debian:<br>
>>>>>>><br>
>>>>>>> <a href="http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597445" target="_blank">http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597445</a><br>
>>>>>>><br>
>>>>>>> Are you guys going to tag a release (e.g. 1.0 or whatever<br>
>>>>>>> call a major/minor version)? It will be a lot easier to<br>
>>>>>>> refer the package to a tagged version (and produce package<br>
>>>>>>> files accordingly).<br>
>>>>>>><br>
>>>>>>> Ciao!<br>
>>>>>>><br>
>>>>>>> Alessandro<br>
>>>>>>><br>
>>>>>>><br>
>>>>>>> 2010/9/17 Venkatesh<br>
>>>>>>> Raghavan<<a href="mailto:raghavan@media.osaka-cu.ac.jp" target="_blank">raghavan@media.osaka-cu.ac.jp</a>>:<br>
>>>>>>>> Hi Alessandro,<br>
>>>>>>>><br>
>>>>>>>> Was great meeting you in Barcelona. Gerald, David and<br>
>>>>>>>> Yoshida have trying to make the Debian package from<br>
>>>>>>>> ZOO-Kernel.<br>
>>>>>>>><br>
>>>>>>>> Maybe you can help us. Also, please consider joining the<br>
>>>>>>>> ZOO-Discuss ML.<br>
>>>>>>>><br>
>>>>>>>> Best<br>
>>>>>>>><br>
>>>>>>>> Venka<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>><br>
>>>>>>><br>
>>>>>>><br>
>>>>>>> -- Alessandro Frigeri, PhD<br>
>>>>>>> _______________________________________________ Zoo-discuss<br>
>>>>>>> mailing list <a href="mailto:Zoo-discuss@gisws.media.osaka-cu.ac.jp" target="_blank">Zoo-discuss@gisws.media.osaka-cu.ac.jp</a><br>
>>>>>>> <a href="http://gisws.media.osaka-cu.ac.jp/mailman/listinfo/zoo-discuss" target="_blank">http://gisws.media.osaka-cu.ac.jp/mailman/listinfo/zoo-discuss</a><br>
>>>>>>><br>
>>>>>><br>
>>>>>><br>
>>>>>><br>
>>>>>><br>
>>>>>>><br>
> _______________________________________________<br>
>>>>>> Zoo-discuss mailing list<br>
>>>>>> <a href="mailto:Zoo-discuss@gisws.media.osaka-cu.ac.jp" target="_blank">Zoo-discuss@gisws.media.osaka-cu.ac.jp</a><br>
>>>>>> <a href="http://gisws.media.osaka-cu.ac.jp/mailman/listinfo/zoo-discuss" target="_blank">http://gisws.media.osaka-cu.ac.jp/mailman/listinfo/zoo-discuss</a><br>
>>>>><br>
>>>>><br>
>>>>>><br>
> _______________________________________________<br>
>>>>> Zoo-discuss mailing list<br>
>>>>> <a href="mailto:Zoo-discuss@gisws.media.osaka-cu.ac.jp" target="_blank">Zoo-discuss@gisws.media.osaka-cu.ac.jp</a><br>
>>>>> <a href="http://gisws.media.osaka-cu.ac.jp/mailman/listinfo/zoo-discuss" target="_blank">http://gisws.media.osaka-cu.ac.jp/mailman/listinfo/zoo-discuss</a><br>
>>>>><br>
>>>><br>
>>>><br>
>>>><br>
>>>> -- Alessandro Frigeri, PhD<br>
>>>> _______________________________________________ Zoo-discuss<br>
>>>> mailing list <a href="mailto:Zoo-discuss@gisws.media.osaka-cu.ac.jp" target="_blank">Zoo-discuss@gisws.media.osaka-cu.ac.jp</a><br>
>>>> <a href="http://gisws.media.osaka-cu.ac.jp/mailman/listinfo/zoo-discuss" target="_blank">http://gisws.media.osaka-cu.ac.jp/mailman/listinfo/zoo-discuss</a><br>
>>><br>
>>> Gérald Fenoy ZOO PSC Chair <a href="mailto:gerald.fenoy@geolabs.fr" target="_blank">gerald.fenoy@geolabs.fr</a><br>
>>><br>
>>><br>
>>> _______________________________________________ Zoo-discuss mailing<br>
>>> list <a href="mailto:Zoo-discuss@gisws.media.osaka-cu.ac.jp" target="_blank">Zoo-discuss@gisws.media.osaka-cu.ac.jp</a><br>
>>> <a href="http://gisws.media.osaka-cu.ac.jp/mailman/listinfo/zoo-discuss" target="_blank">http://gisws.media.osaka-cu.ac.jp/mailman/listinfo/zoo-discuss</a><br>
>>><br>
>>><br>
>>> _______________________________________________ Zoo-discuss mailing<br>
>>> list <a href="mailto:Zoo-discuss@gisws.media.osaka-cu.ac.jp" target="_blank">Zoo-discuss@gisws.media.osaka-cu.ac.jp</a><br>
>>> <a href="http://gisws.media.osaka-cu.ac.jp/mailman/listinfo/zoo-discuss" target="_blank">http://gisws.media.osaka-cu.ac.jp/mailman/listinfo/zoo-discuss</a><br>
>><br>
>> Gérald Fenoy <a href="mailto:gerald.fenoy@geolabs.fr" target="_blank">gerald.fenoy@geolabs.fr</a><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>> _______________________________________________ Zoo-discuss mailing<br>
>> list <a href="mailto:Zoo-discuss@gisws.media.osaka-cu.ac.jp" target="_blank">Zoo-discuss@gisws.media.osaka-cu.ac.jp</a><br>
>> <a href="http://gisws.media.osaka-cu.ac.jp/mailman/listinfo/zoo-discuss" target="_blank">http://gisws.media.osaka-cu.ac.jp/mailman/listinfo/zoo-discuss</a><br>
><br>
> _______________________________________________<br>
> Zoo-discuss mailing list<br>
> <a href="mailto:Zoo-discuss@gisws.media.osaka-cu.ac.jp" target="_blank">Zoo-discuss@gisws.media.osaka-cu.ac.jp</a><br>
> <a href="http://gisws.media.osaka-cu.ac.jp/mailman/listinfo/zoo-discuss" target="_blank">http://gisws.media.osaka-cu.ac.jp/mailman/listinfo/zoo-discuss</a><br>
><br>
<br>
<br>
<br>
--<br>
Alessandro Frigeri, PhD<br>
_______________________________________________<br>
Zoo-discuss mailing list<br>
<a href="mailto:Zoo-discuss@gisws.media.osaka-cu.ac.jp" target="_blank">Zoo-discuss@gisws.media.osaka-cu.ac.jp</a><br>
<a href="http://gisws.media.osaka-cu.ac.jp/mailman/listinfo/zoo-discuss" target="_blank">http://gisws.media.osaka-cu.ac.jp/mailman/listinfo/zoo-discuss</a><br>
</div></div></blockquote></div><br></div>