Can you make a new release of openmpi_ext as dummy package at the same time? Just a new version, that is simply dependent on the new package. Like what it's being done for the time package.
Since MPI is a build dependency of this package, could you list it in the DESCRIPTION file?
What's with the Makefile.OPENMPI1.3.3 file?
The readme file will disappear during installation. Shouldn't it maybe be moved to doc/? And by the way, if both doc/ and devel/ are empty directories, should they be removed?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Can you make a new release of openmpi_ext as dummy package at the same time? Just a new version, that is simply dependent on the new package. Like what it's being done for the time package.
OK.
Since MPI is a build dependency of this package, could you list it in the DESCRIPTION file?
mpi is not require only to build the package but also tu run its functions, so
I'm not sure whether It qualifies as a SystemRequirements or BuildRequires or both.
What is done in other cases?
What's with the Makefile.OPENMPI1.3.3 file?
I don't know it was not created by me. As it does not create problems I'd rather not delete it, but it is OK if I have too.
The readme file will disappear during installation. Shouldn't it maybe be moved to doc/?
no, it contains installation instructions so it's useless once the package has been already installed.
And by the way, if both doc/ and devel/ are empty directories, should they be removed?
OK.
c.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thinking again, I'm not sure it makes sense to have this dummy package
as there is nothing that depends on openmpi_ext, so we could just remove openmpi_ext altogether. I'll leave it to Carnë to choose whether this should be released or not.
Since MPI is a build dependency of this package, could you list it in the DESCRIPTION file?
mpi is not require only to build the package but also tu run its functions, so
I'm not sure whether It qualifies as a SystemRequirements or BuildRequires or both.
What is done in other cases?
Also, how should I write this dependency, as any mpi implementation should (hopefully) work, should this be
SystemRequirements: mpi
BuildRequires: mpi
how do I specify this means the system mpi library rather than the Octave-Forge mpi package?
c.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
As I know nothing about those libraries, I'll leave it to your discretion in how to list on those fields. Note pkg does not do anything about it, it's only meant as a note to downstream packagers. Also, there's a syntax meant to mention package names in certain distributions. From Octave manual:
One further detail to aid the packager is that the SystemRequirements
and BuildRequires keywords can have a distribution dependent section,
and the automatic build process will use these. An example of the
format of this is
BuildRequires: libtermcap-devel [Mandriva] libtermcap2-devel
About meaning the system MPI library instead of an octave package, a dependency on another Octave package would be listed on the Dependencies field. If it's on the SystemRequirements or BuildRequires then it must be an application or library.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Can you make a new release of openmpi_ext as dummy package at the same time? Just a new version, that is simply dependent on the new package. Like what it's being done for the time package.
Since MPI is a build dependency of this package, could you list it in the DESCRIPTION file?
What's with the Makefile.OPENMPI1.3.3 file?
The readme file will disappear during installation. Shouldn't it maybe be moved to doc/? And by the way, if both doc/ and devel/ are empty directories, should they be removed?
On 17 Sep 2013, at 05:37, Carnë Draug carandraug@users.sf.net wrote:
OK.
mpi is not require only to build the package but also tu run its functions, so
I'm not sure whether It qualifies as a SystemRequirements or BuildRequires or both.
What is done in other cases?
I don't know it was not created by me. As it does not create problems I'd rather not delete it, but it is OK if I have too.
no, it contains installation instructions so it's useless once the package has been already installed.
OK.
c.
Thinking again, I'm not sure it makes sense to have this dummy package
as there is nothing that depends on openmpi_ext, so we could just remove openmpi_ext altogether. I'll leave it to Carnë to choose whether this should be released or not.
$ md5sum openmpi_ext-1.1.1.tar.gz
6ff1b2149e2ad0a8494897c396a65905 openmpi_ext-1.1.1.tar.gz
$ md5sum openmpi_ext-1.1.1-html.tar.gz
9d380c36c16e795fd61860bcd5fdfa27 openmpi_ext-1.1.1-html.tar.gz
Last edit: cdf 2013-09-17
On 17 Sep 2013, at 10:13, cdf cdf@users.sf.net wrote:
Also, how should I write this dependency, as any mpi implementation should (hopefully) work, should this be
SystemRequirements: mpi
BuildRequires: mpi
how do I specify this means the system mpi library rather than the Octave-Forge mpi package?
c.
As I know nothing about those libraries, I'll leave it to your discretion in how to list on those fields. Note
pkgdoes not do anything about it, it's only meant as a note to downstream packagers. Also, there's a syntax meant to mention package names in certain distributions. From Octave manual:One further detail to aid the packager is that the SystemRequirements and BuildRequires keywords can have a distribution dependent section, and the automatic build process will use these. An example of the format of this is BuildRequires: libtermcap-devel [Mandriva] libtermcap2-develAbout meaning the system MPI library instead of an octave package, a dependency on another Octave package would be listed on the Dependencies field. If it's on the
SystemRequirementsorBuildRequiresthen it must be an application or library.Here's the new version.
Let me know if you're too busy with GSOC and/or PhD and you want me to do the release myself.
$ md5sum mpi*.tar.gz
90ef3b0245efcc93a51e9ccfb8da2d70 mpi-1.1.1.tar.gz
2114c6578b5876be7eb60932f74666ca mpi-html-1.1.1.tar.gz
Last edit: cdf 2013-09-26
here's the dummy package for openmpi_ext:
$ md5sum openmpi_ext*.gz
0d0d42c27e49f71c905282f8603b88c6 openmpi_ext-1.1.1.tar.gz
4976207ddceb72c6a38871c41a83c68e openmpi_ext-html-1.1.1.tar.gz
Last edit: cdf 2013-09-26