I'm planning on dropping libnc-dap. It is no longer supported and functionality has moved into the netcdf 4 library.
The only package currently requiring libnc-dap is:
octave-forge-0:20090607-17.fc14.i686
Also, apparently octave is planning a 3.4 release this weekend which I would like to see get into F15. These two events I believe will drive the final stake into the heart of the octave-forge package at which point we will need to start packaging the components separately. Since this is how upstream distributes them anyway, I see no reason not to move in this direction in all possible haste. I will try to get back to my earlier efforts on creating a packaging template for octave packages as soon as I can. Any help would be greatly appreciated.
- Orion
On Saturday 05 February 2011 21:11:34 Orion Poplawski wrote:
I'm planning on dropping libnc-dap. It is no longer supported and functionality has moved into the netcdf 4 library.
The only package currently requiring libnc-dap is:
octave-forge-0:20090607-17.fc14.i686
Also, apparently octave is planning a 3.4 release this weekend which I would like to see get into F15. These two events I believe will drive the final stake into the heart of the octave-forge package at which point we will need to start packaging the components separately. Since this is how upstream distributes them anyway, I see no reason not to move in this direction in all possible haste. I will try to get back to my earlier efforts on creating a packaging template for octave packages as soon as I can. Any help would be greatly appreciated.
- Orion
Hi Orion, what has been done here and can I do to help the this effort?
On 03/17/2011 11:48 AM, José Matos wrote:
On Saturday 05 February 2011 21:11:34 Orion Poplawski wrote:
I'm planning on dropping libnc-dap. It is no longer supported and functionality has moved into the netcdf 4 library.
The only package currently requiring libnc-dap is:
octave-forge-0:20090607-17.fc14.i686
Also, apparently octave is planning a 3.4 release this weekend which I would like to see get into F15. These two events I believe will drive the final stake into the heart of the octave-forge package at which point we will need to start packaging the components separately. Since this is how upstream distributes them anyway, I see no reason not to move in this direction in all possible haste. I will try to get back to my earlier efforts on creating a packaging template for octave packages as soon as I can. Any help would be greatly appreciated.
- Orion
Hi Orion, what has been done here and can I do to help the this effort?
- octave 3.4.0 is in F15
- New octave packaging guidelines have been submitted to the FPC. I think there were some questions, but I haven't been contacted directly.
https://fedoraproject.org/wiki/PackagingDrafts/Octave https://fedorahosted.org/fpc/ticket/61
- I've tried to make an oct2spec packaging script, hosted here:
http://git.fedorahosted.org/git/?p=oct2spec.git http://www.cora.nwra.com/~orion/fedora/oct2spec-1.0.0-1.fc14.src.rpm
It's not working at the moment, I seem to have screwed up something with the python packaging. Any help with that would be appreciated.
- I've put a list of octave forge packages here:
https://fedoraproject.org/wiki/OrionPoplawski/Octave_Packages
Perhaps people can sign up there for what packages they want to own. We're going to need to make and review a bunch of packages.
I would also like to see 3.4.0 in EPEL 6.
On Thu, Mar 17, 2011 at 12:00 PM, Orion Poplawski orion@cora.nwra.com wrote:
- New octave packaging guidelines have been submitted to the FPC. I think
there were some questions, but I haven't been contacted directly.
https://fedoraproject.org/wiki/PackagingDrafts/Octave https://fedorahosted.org/fpc/ticket/61
Thanks for doing this. I'm currently trying to package Csdp [1], which comes with an Octave interface, and have been struggling with how to do that, since I know nothing about Octave. That packaging draft really helped. I have some minor comments on it.
First, it shows that a noarch Octave package needs to BR octave-devel. But it looks like octave-devel is only useful for arch-specific Octave packages, isn't it? So shouldn't a noarch Octave package just BR octave?
Second, the %octave_pkg_build macro doesn't quite do what I need. The Csdp sources aren't in the right structure for octave's "pkg build" command, so I have to move stuff around, create a DESCRIPTION file, etc. The end result is that I need to do this:
%octave_cmd pkg build '-verbose' %{_tmppath}/%{name}-%{version}-%{release}.%{_arch} csdp
on a directory named "csdp" in the unpacked sources, rather than on %SOURCE0. Is this unusual? If so, perhaps there is no point in dealing with it.
Now I just have to figure out why Octave is throwing an error on the very last step of the test code and I think the package is ready to go...
References: [1] https://projects.coin-or.org/Csdp/
On 03/17/2011 02:07 PM, Jerry James wrote:
On Thu, Mar 17, 2011 at 12:00 PM, Orion Poplawskiorion@cora.nwra.com wrote:
- New octave packaging guidelines have been submitted to the FPC. I think
there were some questions, but I haven't been contacted directly.
https://fedoraproject.org/wiki/PackagingDrafts/Octave https://fedorahosted.org/fpc/ticket/61
Thanks for doing this. I'm currently trying to package Csdp [1], which comes with an Octave interface, and have been struggling with how to do that, since I know nothing about Octave. That packaging draft really helped. I have some minor comments on it.
First, it shows that a noarch Octave package needs to BR octave-devel. But it looks like octave-devel is only useful for arch-specific Octave packages, isn't it? So shouldn't a noarch Octave package just BR octave?
Sounds correct. Changed.
Second, the %octave_pkg_build macro doesn't quite do what I need. The Csdp sources aren't in the right structure for octave's "pkg build" command, so I have to move stuff around, create a DESCRIPTION file, etc. The end result is that I need to do this:
%octave_cmd pkg build '-verbose' %{_tmppath}/%{name}-%{version}-%{release}.%{_arch} csdp
on a directory named "csdp" in the unpacked sources, rather than on %SOURCE0. Is this unusual? If so, perhaps there is no point in dealing with it.
Hmm, this really was only intended for packaging octave packages like those at the octave forge site http://octave.sourceforge.net/. Those do conform to the standard for octave packages though. Can you post a srpm? I might be able to rework %octave_pkg_build to have the ability to take an argument.
Also, I'm looking into moving the package location into %{_libdir}/octave and will be renaming the %pre macro to be %octave_pkg_preun.
On Thu, Mar 17, 2011 at 2:20 PM, Orion Poplawski orion@cora.nwra.com wrote:
Hmm, this really was only intended for packaging octave packages like those at the octave forge site http://octave.sourceforge.net/. Those do conform to the standard for octave packages though. Can you post a srpm? I might be able to rework %octave_pkg_build to have the ability to take an argument.
A spec file and an SRPM are here: http://jjames.fedorapeople.org/csdp/
The spec file has all the macros from /etc/rpm/macros.octave pasted at the top, because I'm working on a Fedora 14 machine. I tried erasing all of that and building on an F-15 virtual machine, but the build failed at the step where I did "%octave_cmd pkg build '-verbose' %{_tmppath}/%{name}-%{version}-%{release}.%{_arch} csdp", like this:
+ octave -H -q --no-site-file --eval 'pkg build '''-verbose''' /var/tmp/csdp-6.1.1-1.fc15.x86_64 csdp' warning: creating build directory /var/tmp/csdp-6.1.1-1.fc15.x86_64 mkdir (/tmp/oct-DUg3Jt) untar (csdp, /tmp/oct-DUg3Jt) unpack: FILETYPE must be gunzip for a directory error: called from `unpack' in file /usr/share/octave/3.4.0/m/miscellaneous/unpack.m near line 47, column 9 error: called from: error: /usr/share/octave/3.4.0/m/pkg/pkg.m at line 729, column 5 error: /usr/share/octave/3.4.0/m/pkg/pkg.m at line 592, column 3 error: /usr/share/octave/3.4.0/m/pkg/pkg.m at line 464, column 7
error: Bad exit status from /var/tmp/rpm-tmp.LSJPC4 (%build)
You were asking for help, and here I am taking up your time. Please don't spend much effort on this. I just need the Csdp library, not the Octave interface, so if this looks too hairy I can drop Octave support for now.
On 03/17/2011 02:50 PM, Jerry James wrote:
On Thu, Mar 17, 2011 at 2:20 PM, Orion Poplawskiorion@cora.nwra.com wrote:
Hmm, this really was only intended for packaging octave packages like those at the octave forge site http://octave.sourceforge.net/. Those do conform to the standard for octave packages though. Can you post a srpm? I might be able to rework %octave_pkg_build to have the ability to take an argument.
A spec file and an SRPM are here: http://jjames.fedorapeople.org/csdp/
For something like that, I would follow something like plplot and just copy the matlab directory (renaming it) to /usr/share/octave/site/m/Csdp. That should work.
On Thu, Mar 17, 2011 at 3:43 PM, Orion Poplawski orion@cora.nwra.com wrote:
For something like that, I would follow something like plplot and just copy the matlab directory (renaming it) to /usr/share/octave/site/m/Csdp. That should work.
I'll give that a try. Thanks a lot for your help.
- octave-3.4.0-5.fc15 has been submitted:
https://admin.fedoraproject.org/updates/octave-3.4.0-5.fc15
This contains the latest macros and moves package to %{_libdir}/octave from %{_libexecdir}/octave. Please test.
- New octave packaging guidelines have been ratified. Announcement should come soon.
https://fedoraproject.org/wiki/PackagingDrafts/Octave https://fedorahosted.org/fpc/ticket/61
- I've made an oct2spec packaging script, package submission is here:
https://bugzilla.redhat.com/show_bug.cgi?id=692257
It should be basically working. Thanks to José Abílio for helping here.
- I've put a list of octave forge packages here:
https://fedoraproject.org/wiki/OrionPoplawski/Octave_Packages
Perhaps people can sign up there for what packages they want to own. We're going to need to make and review a bunch of packages.
- I would also like to see 3.4.0 in EPEL 6, but will wait until we are comfortable with it in F15.
On 03/30/2011 02:35 PM, Orion Poplawski wrote:
- octave-3.4.0-5.fc15 has been submitted:
https://admin.fedoraproject.org/updates/octave-3.4.0-5.fc15
This contains the latest macros and moves package to %{_libdir}/octave from %{_libexecdir}/octave. Please test.
This is pushed to stable now.
- I've made an oct2spec packaging script, package submission is here:
Updated.
- I've put a list of octave forge packages here:
https://fedoraproject.org/wiki/OrionPoplawski/Octave_Packages
Perhaps people can sign up there for what packages they want to own. We're going to need to make and review a bunch of packages.
I've signed up for image and octcdf and put links to the review requests on the above page.
On 04/06/2011 09:46 AM, Orion Poplawski wrote:
On 03/30/2011 02:35 PM, Orion Poplawski wrote:
- I've made an oct2spec packaging script, package submission is here:
Built and updates submitted for F14 and F15.