[Pkg-giraffe-discuss] Try out to package kopano-webapp-plugin-files* fails

[Marco Costantino]

Carsten

I think kopano won't package all plugins in one single package as by having them separately they can be marketed separately.  Those plugins being files or web meetings or smime are the value added kopano plugins therefore rightly so they do want to sell them separately depending on the editions. 

Marco

On 10 December 2016 09:04:31 GMT+00:00, Carsten Schoenert <c.schoenert at t-online.de> wrote:
>Hello,
>
>On 08.12.2016 10:27, Marco Costantino wrote:
>> Hi
>> 
>> Perhaps the easiest even if duplicates code would be to have the
>> code in every plugin?
>> 
>> This way the plugin are self contained and do not depend on anything
>> else, if I have understood correctly that is. 
>
>well we obviously don't want duplicated code. So I disagree here. Every
>plugin is depending on the core code, the kopano-webapp and sometimes
>maybe on other plugins. So the correct way is declare the right
>dependencies between the packages.
>
>[...]
>>> Yup, it's sort of the right way. The WebApp has 'build tools' in the
>>> tools directory (for concatenating css. JavaScript) and
>>> server/manifest.dtd  
>>> to verfiy the manifest.xml file
>>>
>>> Since we didn't want to copy these files to every plugin, we
>internally
>>> have created a simple "kopano-webapp-buildtools" package.
>>> Which in reality should be a split package from kopano-webapp. 
>>>
>>> To be honest it's a bit ugly, looking at our debian.rules file:
>>>
>>> override_dh_auto_install:
>>> 	install -d -m 755 $(INSTDIR)$(TOOLSDIR)
>>> 	cd tools && ant && cd ../
>>> 	cp -rf server tools plugins/ $(INSTDIR)$(TOOLSDIR)/
>>>
>>> And in our plugin we build it as following, (and make depend on
>>> buildtools)
>>>
>>> ant -Dtools-folder=/usr/share/kopano-webapp-buildtools/tools/  \
>>>       -Dserver-folder=/usr/share/kopano-webapp-buildtools/server/ 
>>>    -Dtarget-folder=deploy -Dplugin-folder=files -Dplugin=files
>deploy;
>>>
>>>
>>> I hope that helps, otherwise I can probably share the
>>> kopano-webapp-buildtools package.
>>> I think copying the whole plugins directory is a bug.. :) I think it
>>> really needs plugins/build.xml to be copied for the plugin to build.
>
>Why Kopano can't collect all the various plugins into one source
>package? This way the zarafa-webapp was working and it was the best way
>I can imagine in a backview. Yes, there can be exceptions of course.
>
>If you cut all in small pieces every time one tiny thing is changing
>you
>have to check and test all the stuff with a lot of effort. And this
>makes packaging more difficult.
>I see no problem to do so as all the installation work is done by the
>package tools in the distributions. I currently have really some
>problems to collect the various extras into packages in a valuable way.
>And right now I'm out of time for doing more packaging ...
>
>-- 
>Regards
>Carsten Schoenert
>
>_______________________________________________
>Pkg-giraffe-discuss mailing list
>Pkg-giraffe-discuss at lists.alioth.debian.org
>http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-giraffe-discuss

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-giraffe-discuss/attachments/20161210/da3cb7d4/attachment.html>