Hi Paulo,<br><br>Thanks very much for your e-mail. I am switching the conversation over the CoinBinary project mailing list (I just realized that the project's XML page says that the mailing list for the project is coin-discuss---I will update that). One of the goals of the CoinBinary project (and of the creation of the CoinALl package) since the beginning has been to make it possible to put together packages for Linux distributions (as well as installers for other platforms). We have made a lot of changes to the build system in recent years to support this eventual goal, but have lacked the manpower to follow through in doing the packaging. I'll try to answer some of your questions below, but we will probably have to have a bit of back and forth to work everything out. <br>
<br><div class="gmail_quote">On Sun, Sep 23, 2012 at 5:50 PM, 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 made an experimental coin-or package, at first from the CoinAll tarball,<br>
any feedback is welcome, e.g. if it is really desirable to make a package for<br>
every sub project, for easier updates, etc (I am more friendly to CoinAll<br>
because it is supposed to be tested that all bits work together).<br></blockquote><div><br><br>The purpose of CoinAll was exactly this. For reasons we can discuss in more detail, I think it is best to have a separate package for each project (CoinUtils, Clp, Cbc, etc.). We have made a number of design choices with the build system to support this.<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Running fedora-review on the package I see these fatal errors:<br>
<br>
coin-or.x86_64: E: zero-length /usr/share/coin/doc/Data/miplib3/AUTHORS<br>
coin-or.x86_64: E: zero-length /usr/share/coin/doc/Data/miplib3/LICENSE<br>
coin-or.x86_64: E: zero-length /usr/share/coin/doc/Data/Netlib/README<br>
coin-or.x86_64: E: zero-length /usr/share/coin/doc/Data/Sample/AUTHORS<br>
coin-or.x86_64: E: zero-length /usr/share/coin/doc/Data/Sample/LICENSE<br>
coin-or.x86_64: E: zero-length /usr/share/coin/doc/Data/Netlib/LICENSE<br>
coin-or.x86_64: E: zero-length /usr/share/coin/doc/Data/miplib3/README<br>
coin-or.x86_64: E: zero-length /usr/share/coin/doc/Data/Sample/README<br>
coin-or.x86_64: E: zero-length /usr/share/coin/doc/Data/Netlib/AUTHORS<br>
<br>
Maybe those were supposed to be symbolic links?<br></blockquote><div><br>The data projects are strange beasts---they consist of data files that are part of widely distributed test sets. The origin of many of the files is difficult to ascertain, so creating AUTHORS, README, and even LICENSE files is difficult. We have had on our long-term TODO list to come up with a solution for this, but in any case, they are not necessary for anything else to work---they are mainly there for unit testing. We made them separate projects to keep them isolated (to keep the provenance of other projects cleaner) and to make it possible to choose whether to install them more easily.<br>
<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
The warnings from fedora-review are issues that I can easily handle,<br>
for example, \r\n line endings on some files, sources with executable bit<br>
set, etc. These may be of special interest:<br>
<br>
coin-or.x86_64: W: no-manual-page-for-binary cbc<br>
coin-or.x86_64: W: no-manual-page-for-binary blis<br>
coin-or.x86_64: W: no-manual-page-for-binary symphony<br>
coin-or.x86_64: W: no-manual-page-for-binary clp<br>
coin-or.x86_64: W: no-manual-page-for-binary OSSolverService<br>
<br>
help2man is not of much use for these, but it should be easy to create<br>
simple manpages based on documentation.<br></blockquote><div><br>Yes, this should be asy to do.<br> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Another issue, I see that the COIN-OR-1.6.2-linux-x86_64-gcc4.4.5.tar.gz<br>
tarball does not distribute the AUTHORS, README and LICENSE files,<br>
but does distribute several pdf files. I do not see a make target to create<br>
those, but I may be missing something trivial.<br></blockquote><div><br>You are correct that there is no target to create the PDF files that are part of these, but we could create a target for that pretty easily. I'm not sure what you mean about the tarball not distributing AUTHORS, README, etc. Those should be installed for each project in the /share/doc directory.<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
The initial package is at:<br>
Spec: <a href="http://fedorapeople.org/~pcpa/coin-or.spec" target="_blank">http://fedorapeople.org/~pcpa/coin-or.spec</a><br>
SRPM: <a href="http://fedorapeople.org/~pcpa/coin-or-1.6.0-1.fc19.src.rpm" target="_blank">http://fedorapeople.org/~pcpa/coin-or-1.6.0-1.fc19.src.rpm</a></blockquote><div> <br>Keep us posted and we'll be happy to help in whatever way we can.<br>
<br>Ted<br>-- <br></div></div>Dr. Ted Ralphs<br>Associate Professor, Lehigh University<br><a href="tel:%28610%29%20628-1280" value="+16106281280" target="_blank">(610) 628-1280</a><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>