[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Package and script naming



Hello,
For my question #2, I've looked in pitivi, and they do something like this :
(in an imaginary executable named script/spam, where a package "spam"
also exists in the same dir as "scripts".)

#!/usr/bin/env python
import os
import sys

def _is_in_devel():
    d = os.path.split(os.path.dirname(os.path.abspath(__file__)))[0]
    return (
        os.path.exists(os.path.join(d, ".hg")) or
        os.path.exists(os.path.join(d, ".svn"))
        )

if __name__ == "__main__":
    if _is_in_devel():
        d = os.path.split(os.path.dirname(os.path.abspath(__file__)))[0]
        sys.path.insert(0, d)
    from spam import runner
    runner.run()


2010/1/5 Alexandre Quessy <alexandre@quessy.net>:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hello everyone,
> I am in the process of putting finishing touches to a few new Debian
> Python packages and applications to go though the Debian-mentor process
> in order to become part or the debian-python team ! Meanwhile, I have a
> few questions. I have two to ask now.
>
> I am working on a Python application for the Debian and Ubuntu GNU/Linux
> distributions. For this one, I am not sure about the naming scheme, so I
> thought I should ask here.
>
> The application is named "lunch", and should provide the following files:
>  * /usr/share/applications/lunch.desktop
>  * /usr/share/man/man1/lunch.1
>  * /usr/share/pixmaps/lunch.png
>  * /usr/bin/lunch
>  * /usr/share/pyshared/lunch/ : a Python package with a few modules.
>  * /usr/share/pyshared/lunch-0.1.1.egg-info/ : I guess an egg will be there.
>
> So, I guess, in the setup.py file, the "name" keyword-argument of the
> setup function should be "lunch". Does that mean that my Debian package
> should be named "python-lunch", or can it be named simply "lunch" ?
>
> An other question : since the executable and the package have the same
> name, the executable needs to be in script/lunch. This means that I need
> to run it with a command such as the following :
>
>  PYTHONPATH=$PWD scripts/lunch
>
> If I want to test my executable, from within the repository, without the
> need to install the Python package, even using "sudo python setup.py
> develop". Anyone has a workaround to avoid typing that much ? I would
> rather simply type "./scripts/lunch" to run my app.
>
> Thanks !
>
> Alexandre Quessy
> http://alexandre.quessy.net
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iQIcBAEBAgAGBQJLQzmYAAoJEJQ0pOgl2qx1KrQP/3A93MA6BxskkNdMEDCeSLY3
> GNDXvZZop5GSCh4E9QxiL34oUoba3E2vNUeaGUxRJQNOy3Iyq9ZmcB6t9dH13OKX
> QGTX3idMqc/zfmHiwv6F3+437tZqFXtb48ZKMM2U/5IQwG0BDGg0pzvgQ602NKCn
> bp5JttT2SEoEl/Dh17XaoVrod7LLpqNLTOmpNWHewR5JXBPAjIFVeqZjMplHNKC4
> IziOFuafqQ0MPmxEdx10UzEeCDE8TZY7RfqKsa2uthZc44rSzoIz2IkNgXJLjmgl
> noX7tlVduBfFogPKnDA6EHH+6k7YB/6SKbxKNc5p0yO2GWjamWUR9Hg3um6R0Mhj
> 3/GsaW6SJ8c7YA0DqWogKNOfyGv7EjTsMBJmeALsjFGMBUpG80TQr1l2gDfn5xpT
> +qE3Ygp3p4CuDXJ+kkObEVrBvNRCtl3ialfdxu/oGAKiZw4zuMoWLnI3mGz3c6Rz
> dNd1wAXrerhTfcKFwJqUVGk9cN0lOie/33tpTP8KjPDS6/WHFywWFceGvOm8eBpi
> 2RoqnoO4ghuf6rNTb1GSOl9/X5s22LzfWGGS+BOiGpMDgD/pciH7SLUq6dS8+eNN
> Di9PbBiTSLwRbB91f03WjLGkCLrYDDPMPh6v6Xj7NYlCLwSPhTUzKVzBI8lPR76g
> Vqqi1kh/NQbGs8ODv/mD
> =UcvR
> -----END PGP SIGNATURE-----
>



-- 
Alexandre Quessy
http://alexandre.quessy.net/


Reply to: