> On Apr 30, 2016, at 15:42, Scott Hannahs <shann...@users.sourceforge.net>
> wrote:
>
> Unfortunately I maintain a python utility for fink. But not being terribly
> up on the versioning issues with python I am having some problems with some
> utilities. I would appreciate a bit of help from the collective wisdom.
>
> I have set up a couple of python libraries by copying another library I am
> updating. But they each gives a different error.
>
> pbr-py: gives the following
> Validating .deb dir /sw/src/fink.build/root-pbr-py27-1.9.1-1...
> Error: File in a language-versioned package does not have a pathname specific
> to that version.
> Offending file: /sw/bin/pbr
>
> pycryptopp gives the following:
> Validating .deb dir /sw/src/fink.build/root-pycryptopp-py27-0.7.1-1...
> Error: File in a language-versioned package does not have a pathname specific
> to that version.
> Offending file: /sw/share/doc/pycryptopp/COPYING.GPL
> Offending file: /sw/share/doc/pycryptopp/COPYING.MIT.txt
> Offending file: /sw/share/doc/pycryptopp/COPYING.SPL.txt
> Offending file: /sw/share/doc/pycryptopp/COPYING.TGPPL.rst
> Offending file: /sw/share/doc/pycryptopp/README.rst
>
> As far as I can tell fink wants to version the utility in sw/bin and the
> documentation in /sw/share/doc
> This is fine, but I don’t see the switch to tell fink or the install script
> to do special handling for the tools or the documentation.
>
> Any suggestions of where to go for an example on how to handle this? I find
> it odd, because fink automatically did this for the lockfile-py27
> installation that I used as a template.
> For example on the pycryptopp library I use
> InstallScript: %p/bin/python%type_raw[python] setup.py install --prefix=%p
> --root=%d
> DocFiles: COPYING.GPL COPYING.MIT.txt COPYING.SPL.txt COPYING.TGPPL.rst
> MANIFEST.in NEWS.rst PKG-INFO README.ed25519.rst README.rst
>
> -Scott
>
There’s no magic associated with Python builds. Any necessary tweaks are
generally done manually. Without seeing your .info files, it’s hard to say
what’s wrong, but here are some ideas to look at:
1) Your pbr package looks like an executable rather than a python module.
It’s often best not to use Type: python in executable packages, particularly if
they only use one Python version, since that avoids triggering the validator
check for language versioning.
If you’re allowing for multiple python versions for an executable, then the way
to go is to rename the executable, e.g. to pbr-%type_raw[python] or
pbr-%type_pkg[python] and then to use update-alternatives to allow users to
select which one becomes “pbr”. sci/pymol-py.info is an example of how to do
this for multiple versions.
2) For pytcryptopp, it looks like the documents somehow got installed in
%i/share/doc/%{Ni} rather than %i/share/doc/%N. If we take lockfile-py27 as an
example its DocFiles get installed as follows:
/sw/share/doc/lockfile-py27/ACKS
/sw/share/doc/lockfile-py27/doc
/sw/share/doc/lockfile-py27/doc/source
/sw/share/doc/lockfile-py27/doc/source/conf.py
/sw/share/doc/lockfile-py27/doc/source/index.rst
/sw/share/doc/lockfile-py27/doc/source/Makefile
/sw/share/doc/lockfile-py27/LICENSE
/sw/share/doc/lockfile-py27/PKG-INFO
/sw/share/doc/lockfile-py27/README
/sw/share/doc/lockfile-py27/RELEASE-NOTES
--
Alexander Hansen, Ph.D.
Fink User Liaison
------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel
