Update of /cvsroot/fink/experimental/alexkhansen/common/finkinfo/sci
In directory vz-cvs-3.sog:/tmp/cvs-serv28262

Added Files:
        octcdf-oct.info 
Log Message:
Works on 10.5/powerpc, but had a strange failure on 10.7/x86_64.  
Additional testing is in order.


--- NEW FILE: octcdf-oct.info ---
Info2: <<
Package: octcdf-oct%type_pkg[oct]
Version: 1.0.13
Type: oct (3.2.4), forge (octcdf)
Revision: 1
Maintainer: Alexander Hansen <alexkhan...@users.sourceforge.net>
# unfortunately, Homepage won't do types
Homepage: http://octave.sourceforge.net/general/index.html 
Description: A NetCDF interface for octave
DescDetail: <<
This package is DAP-enabled via the  NetCDF3 implementation in libnc-dap3.
It contains the following functions and examples.
NetCDF:
        ncautonan
        ncautoscale
        ncbyte
        ncchar
        ncdouble
        ncdump
        ncfloat
        ncint
        nclong
        ncshort
        netcdf_setup
        ncatt
        ncclose
        ncdatatype
        ncdim
        ncenddef
        ncname
        ncredef
        ncsync
        ncvar
        netcdf
        ncisrecord
Examples:
        example_netcdf
        example_opendap
<<
License: GPL

# All octave-forge packages have to have the following BuildDepends:
#  octave%type_pkg[oct]-dev | octave%type_pkg[oct]-atlas-dev,
# fftw3, 
# ( %type_pkg[oct] = 305 ) hdf5.7-oldapi,
# ( %type_pkg[oct] != 305 ) hdf5.7
#
# Packages which serve only Octave-3.0.5 or only Octave > 3.0.5 need
# not use the conditional, of course.

BuildDepends: <<
  octave%type_pkg[oct]-dev | octave%type_pkg[oct]-atlas-dev,
  fftw3, libnc-dap3 (>= 1:3.7.3-4),
  ( %type_pkg[oct] = 305 ) hdf5.7-oldapi,
  ( %type_pkg[oct] != 305 ) hdf5.7
<<
Depends: << 
  octave%type_pkg[oct] | octave%type_pkg[oct]-atlas,
  libnc-dap3-shlibs (>= 1:3.7.3-4)
  <<
Conflicts: octave-forge, octave-forge-%type_raw[forge] (<< 1.0.7-999)
Replaces: octave-forge-%type_raw[forge] (<< 1.0.7-999)

Source-MD5: 318d8d3a6272ddbfef7f259dd3998013

#### Insert required changes here ####

CompileScript: <<
#!/bin/sh -ev
export OCTAVE=%p/bin/octave-%type_raw[oct]
%p/share/octave/%type_raw[oct]/scripts/octave-forge-compile.sh 
%type_raw[forge]-%v
<<

######################################

# Do not change anything from this point down, unless absolutely necessary,
# since the foo-oct%type_pkg[oct] packages are designed to be built/installed
# in the same way.

Source: mirror:sourceforge:octave/%type_raw[forge]-%v.tar.gz

NoSetCPPFLAGS: true
NoSetLDFLAGS: true
SetLIBRARY_PATH: /usr/X11R6/lib:%p/lib
SetMAKEFLAGS: -j1

InstallScript: << 
        #!/bin/sh -ev
        %p/share/octave/%type_raw[oct]/scripts/octave-forge-install.sh 
%type_raw[forge]-%v %i %b
        mkdir -p %i/share/octave/%type_raw[oct]/%type_raw[forge]-%v
        # copy template scripts
        cp %p/share/octave/%type_raw[oct]/scripts/octave-forge-prerm 
%p/share/octave/%type_raw[oct]/scripts/octave-forge-postinst 
%i/share/octave/%type_raw[oct]/%type_raw[forge]-%v
        cd %i/share/octave/%type_raw[oct]/%type_raw[forge]-%v
        sed -i -e 's/@PKGNAME@/%type_raw[forge]-%v/' octave-forge-postinst
        sed -i -e 's/@PKGNAME@/%type_raw[forge]/' octave-forge-prerm
        chmod a+x octave-forge*
<<

PostInstScript:  <<
        if [ -s %p/var/octave/%type_raw[oct]/octave_packages ] && [ -f 
%p/var/octave/%type_raw[oct]/octave_packages ] 
        then 
                
%p/share/octave/%type_raw[oct]/%type_raw[forge]-%v/octave-forge-postinst
        else
                mv 
%p/share/octave/%type_raw[oct]/packages/%type_raw[forge]-%v/octave_packages 
%p/var/octave/%type_raw[oct]/octave_packages
        fi
<<

PreRmScript: 
%p/share/octave/%type_raw[oct]/%type_raw[forge]-%v/octave-forge-prerm

DescPackaging: <<
Common for all octave-forge packages.

We read in postinst and prerm template scripts installed by octaveN and modify
them to use the name of this package because Octave's package manager can't 
cope with non-literal arguments.

The Type: forge (pkgname) is used to minimize what needs to be changed when
using this .info file as a template.
<<
<<

------------------------------------------------------------------------------
Doing More with Less: The Next Generation Virtual Desktop 
What are the key obstacles that have prevented many mid-market businesses
from deploying virtual desktops?   How do next-generation virtual desktops
provide companies an easier-to-deploy, easier-to-manage and more affordable
virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/
_______________________________________________
Fink-commits mailing list
Fink-commits@lists.sourceforge.net
http://news.gmane.org/gmane.os.apple.fink.cvs

Reply via email to