On Sat, 2019-01-12 at 18:43 +0100, Vojtěch Zeisek wrote:
Dne pátek 4. ledna 2019 13:55:56 CET jste napsal(a):
Vojtěch Zeisek writes:
Well, my packaging experience is zero. My Linux experience is considerable, but I'm not programmer. As a biologist, I'd like to see some
included. From the original list namely ugene. And some more, of
I wonder if I'd be able (by means of skills and time/effort
package software I need for my work (some is not very well
Well, now I just compile what I need. So... If we consider software with simple (or no) dependences, I
follow steps in README - (./congifue), make, (make install); is packaging in OBS significantly more difficult...?
The short answer would be: if all you need to do is just 'configure; make; make install' it is problably not too difficult. The more in-depth answer would be: it depends - there are quite a few guidelines about the installation to be followed and make to sure that 'rpmlint' is reasonably happy, thus files may have to be moved around after a 'make install' - at least if you plan to bring the package into oS:Factory later. Generally, when you pick up an existing package most of the things have been done already - often it just to update the source tarball or fix a build. On most of the guidelines there is pretty good documentation around - like:
The simplest way to get started is to start with an existing package or use a similar type of package as a guide and only worry about the documentation if there are issues. Of course, you can always ask here (there are other MLs for packaging questions, but they have a lot more traffic).
Hi, thank You for the introduction. I forked UGENE to https://build.opensuse.org/package/show/home:vojtae us/UGENE but it seems to be too complicated building for newbie. So I tried with https://github.com/stamatak/standard-RAxML in https:// github.com/stamatak/standard-RAxML which has really trivial compilation. But the problem is this software (and many others I use) doesn't define 'make install' (very often it is enough to run just 'make' and then copy manually binary to ~/bin/). So my question is what what to write to %install section of the specfile. I "just" need to copy raxmlHPC* to /usr/bin/ or so. As documentation of this popular tool is, ehm, very brief, I have honestly no idea what is the license of it, if I need gcc or gcc-c++ and what I need to compile pthreads and mpi versions... Vojtěch
Hello Vojtěch, as I contributed some optimization to RAxML when I worked at the institute where it was developed I know the build system quite well. The main problem for packaging this software is that it relies quite heavy on the vector registers of the used CPUs and the optimization for it. So we would have binaries which would not run on all x86 systems, which may be problematic for the packaging policy. A solution would be the HPC modularized version using multibuild. I can look into this when I have some more time. One questions sill arises, as RAxML itself is deprecated. Do you have plans to use ExaML?
kind regards, Christian