<br><br><div class="gmail_quote">On Sat, Nov 10, 2012 at 7:57 AM, Paulo César Pereira de Andrade <span dir="ltr"><<a href="mailto:paulo.cesar.pereira.de.andrade@gmail.com" target="_blank">paulo.cesar.pereira.de.andrade@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Hi,<br>
<br>
I have a prototype all in one "coin-or" package and prototype split<br>
all projects in different packages naming them "coinor-*" at<br>
<a href="http://pcpa.fedorapeople.org/coinor" target="_blank">http://pcpa.fedorapeople.org/coinor</a><br>
<br>
I would like some feedback before making a formal request<br>
for inclusion in the fedora distribution.<br>
<br>
Main issues I have are:<br>
<br>
o Sub project tarballs include all of their dependencies. The reason<br>
probably is to make it self contained and reduce bug reports<br>
due to non matching versions. But I may need to repackage<br>
tarballs to have it accepted in Fedora due to data/examples<br>
missing license information<br></blockquote><div><br>A while back, we changed the configure scripts so that you could easily check out and build the projects individually for this exact reason. If you take just the subfolder Xxx within project Xxx, you can build in that subfolder and link the resulting library against other already installed projects. The only caveat is that you have to build them in the right order (that's what the configure script in the root directory takes care of for you). A simple script could essentially do the same job. All the relevant license, documentation, examples, etc. for each project are located in the subfolder. Would it be sufficient to just take this part of the posted tarballs? If not, it should be relatively easy to create tarballs without dependencies and post those also. You are correct for the reasoning for the current tarballs including all dependencies. <br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
o Data and examples information is very desirable, to know<br>
what could be packaged, but I am afraid they do not have<br>
a license (e.g. <a href="http://www.coin-or.org/download/source/Data/" target="_blank">http://www.coin-or.org/download/source/Data/</a><br>
contents of Data-*.tgz)<br></blockquote><div><br>Yes, that's always been a problem. We discussed it and made an effort to clean this up some time ago, trying to identify the source for each file and get the owner to provide a license, but this was a losing game and didn't go far. Unfortunately, most of the standard test instances that are out there are unlicensed. I will bring this up again with the board and see what we can do.<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
o I did choose "coinor-*" to match Debian naming, but maybe I<br>
should use "coin-or-*", suggestions? :-)<br></blockquote><div><br>I guess I prefer "coin-or" because it then matches the URL.<br><br>Ted <br></div></div>-- <br>Dr. Ted Ralphs<br>Associate Professor, Lehigh University<br>
(610) 628-1280<br>ted 'at' lehigh 'dot' edu<br><a href="http://coral.ie.lehigh.edu/~ted" target="_blank">coral.ie.lehigh.edu/~ted</a><br><br>