[ZOO-Discuss] ZOO Debian Package

Mon Sep 20 15:07:15 PDT 2010

Someday ZOO could hopefully be more than WPS
only.

My suggestion would be to name the package as
zoo-kernel with subsequent release zoo-services
and zoo-api.

Since multi-language support is one of the
main features of the ZOO-Kernel, the present release
(ZOO-Kernel-1.0.1) could C/C++, Fortran and Python
support. Future stable release (ZOO-Kernel-1.2.X) could
include support for javascript and other newly
supported languages.

ZOO-Services and ZOO-API could be released as independent
packages.

Also a possibility of releasing ZOO-Bundle (which includes
ZOO-Kernel, ZOO-Services and ZOO-API) in the future.

Best

Venka

On 2010/09/20 22:15, Gérald Fenoy wrote:
> Hi Daniel, yes you're right, maybe better to keep WPS in the package
> name.
>
> I agree also that the zoo-service and zoo-api can be installed as
> independent packages. But if we use it this way, then how can we
> provide the ZOO Kernel ? I mean that the compilation process of the
> ZOO Kernel imply that each requested Languages support have to be
> compiled at the same time. Or do we need to plan to provide multiple
> "zoo-wps" packages for each support ? I mean something like :
> zoo-wps-std for ZOO Kernel with C/C++, Fortran and Python support,
> then zoo-wps-javascript for another one including the later and with
> the javascript addition and so on ?
>
> I don't know how to do this in an efficient way.
>
> Let me know what you think, Regards,
>
> Le 20 sept. 2010 à 14:39, Daniel Kastl a écrit :
>
>> Hi Gerald,
>>
>> Is ZOO-Project going to be more than WPS? Alessandro's proposal
>> idea to call it "zoo-wps" isn't bad IMO. Another idea would be - in
>> case ZOO Services and API could be installed extra - to split them
>> in packages like "zoo-kernel", "zoo-services", "zoo-api" with being
>> "zoo-kernel" required for others.
>>
>> Well, shouldn't become to complicated on the other hand.
>>
>> Daniel
>>
>>
>>
>> 2010/9/20 Gérald Fenoy<gerald.fenoy at geolabs.fr> Hi Alessandro, nice
>> to hear  from you.
>>
>> I think it can be better to use ZOO-Project, if this is acceptable
>> in Debian packaging name. If not then maybe you can use
>> zoo-project.
>>
>> We will create a branch and tag officially in some days, we need to
>> finalize the Perl support integration first. It was currently
>> tested by David Saggiorato on his own (some part was already
>> integrated in the SVN source tree). We also need to add a ZOO
>> Service Provider which will access some shared memory to get
>> information on the current status of a process. I think that those
>> two enhancement can be finalized really soon and then we can tag as
>> 1.0.1 version. Other plan for the 2.0 version will start next week,
>> it will include the modification of service functions signature,
>> the main reason for creating a new version.
>>
>> Please use the SVN source tree and not the archive 1.0 you talked
>> about, indeed we have to provide the new version of the archive
>> soon for the new version present in SVN.
>>
>> If you need the branch quickly please let me know, we will create
>> it faster than we planned to do.
>>
>> Hope to hear from you, best regards,
>>
>>
>> Le 20 sept. 2010 à 13:22, Alessandro Frigeri a écrit :
>>
>>> Hei Nick, Venka + zooers,
>>>
>>> thanks for the details.  Sorry, I've missed the 1.0 was there
>>> already there,
>>> http://www.zoo-project.org/dl/ZOO-Kernel-1.0.tar.bz2, i'll submit
>>> un update to our request to debian.
>>>
>>> Also, I've found there is already a package named "zoo", to
>>> manipulate zoo archives.  So we can go with with "zoowps"
>>> "zoo-wps" or whatever is good to differentiate from the other
>>> package.  Suggestions are welcome so we can start up in good
>>> shape with debian and the ubuntu packages.
>>>
>>> For the version scheme, it seems ok to me.  Nick, let's
>>> experiment an svn copy trunk to some 1.0.x tag.
>>>
>>> Alessandro
>>>
>>>
>>> 2010/9/20 Venkatesh Raghavan<raghavan at media.osaka-cu.ac.jp>:
>>>> Hi Alessandro,
>>>>
>>>> Thanks for the follow-up at debian/ubuntu miniconf regarding
>>>> ZOO
>>>>
>>>> I think ZOO could follow the similar scheme as GRASS GIS as
>>>> below;
>>>>
>>>> Version number scheme:
>>>>
>>>> * first number: major release number * secondary number: minor
>>>> release number (stable/development indicator) * third number:
>>>> revision
>>>>
>>>> Scheme for ZOO-Kernel 1.0.1 which is presently available would
>>>> be as follows
>>>>
>>>> a) 1 being the major release number b) 0 being the minor
>>>> release number c) 1 being the revision
>>>>
>>>> Any suggestions from others?
>>>>
>>>> Best
>>>>
>>>> Venka
>>>>
>>>> On 2010/09/20 6:00, nicolas bozon wrote:
>>>>> Hi Alessandro,
>>>>>
>>>>> Thanks for the request to Debian ! ZOO Kernel was released on
>>>>> April 2010 under 1.0 version. We are now under the 1.0.1
>>>>> since last week, as the svn was updated with new version by
>>>>> gerald I think we still have to improve the branching, you're
>>>>> right. Best,
>>>>>
>>>>> Nick
>>>>>
>>>>>
>>>>> 2010/9/19 Alessandro Frigeri<afrigeri at unipg.it>
>>>>>
>>>>>> Hi zooers,
>>>>>>
>>>>>> The debian/ubuntu mini conf was very fruitful - nice ideas
>>>>>> and nice people.  For zoo, I've placed a request on
>>>>>> debian:
>>>>>>
>>>>>> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597445
>>>>>>
>>>>>> Are you guys going to tag a release (e.g. 1.0 or whatever
>>>>>> call a major/minor version)?  It will be a lot easier to
>>>>>> refer the package to a tagged version (and produce package
>>>>>> files accordingly).
>>>>>>
>>>>>> Ciao!
>>>>>>
>>>>>> Alessandro
>>>>>>
>>>>>>
>>>>>> 2010/9/17 Venkatesh
>>>>>> Raghavan<raghavan at media.osaka-cu.ac.jp>:
>>>>>>> Hi Alessandro,
>>>>>>>
>>>>>>> Was great meeting you in Barcelona. Gerald, David and
>>>>>>> Yoshida have trying to make the Debian package from
>>>>>>> ZOO-Kernel.
>>>>>>>
>>>>>>> Maybe you can help us. Also, please consider joining the
>>>>>>> ZOO-Discuss ML.
>>>>>>>
>>>>>>> Best
>>>>>>>
>>>>>>> Venka
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> -- Alessandro Frigeri, PhD
>>>>>> _______________________________________________ Zoo-discuss
>>>>>> mailing list Zoo-discuss at gisws.media.osaka-cu.ac.jp
>>>>>> http://gisws.media.osaka-cu.ac.jp/mailman/listinfo/zoo-discuss
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>
_______________________________________________
>>>>> Zoo-discuss mailing list
>>>>> Zoo-discuss at gisws.media.osaka-cu.ac.jp
>>>>> http://gisws.media.osaka-cu.ac.jp/mailman/listinfo/zoo-discuss
>>>>
>>>>
>>>>>
_______________________________________________
>>>> Zoo-discuss mailing list
>>>> Zoo-discuss at gisws.media.osaka-cu.ac.jp
>>>> http://gisws.media.osaka-cu.ac.jp/mailman/listinfo/zoo-discuss
>>>>
>>>
>>>
>>>
>>> -- Alessandro Frigeri, PhD
>>> _______________________________________________ Zoo-discuss
>>> mailing list Zoo-discuss at gisws.media.osaka-cu.ac.jp
>>> http://gisws.media.osaka-cu.ac.jp/mailman/listinfo/zoo-discuss
>>
>> Gérald Fenoy ZOO PSC Chair gerald.fenoy at geolabs.fr
>>
>>
>> _______________________________________________ Zoo-discuss mailing
>> list Zoo-discuss at gisws.media.osaka-cu.ac.jp
>> http://gisws.media.osaka-cu.ac.jp/mailman/listinfo/zoo-discuss
>>
>>
>> _______________________________________________ Zoo-discuss mailing
>> list Zoo-discuss at gisws.media.osaka-cu.ac.jp
>> http://gisws.media.osaka-cu.ac.jp/mailman/listinfo/zoo-discuss
>
> Gérald Fenoy gerald.fenoy at geolabs.fr
>
>
>
>
>
>
> _______________________________________________ Zoo-discuss mailing
> list Zoo-discuss at gisws.media.osaka-cu.ac.jp
> http://gisws.media.osaka-cu.ac.jp/mailman/listinfo/zoo-discuss