I'd be expecting these files under /usr/share/appname and being read only...
I don't agree with Data files should never be installed to package
directories... LFHS is not a religion. I can see cases where is not
appropriate.
The main difference could be a library vs an application case: they
On 19 Nov, 2012, at 20:26, PJ Eby p...@telecommunity.com wrote:
Data files should never be installed to package directories. But I'm not
aware of any good reason why resource files should ever be installed anywhere
*else*.
To be (too) snarky: because the FHS says so.
Less snarky,
Can you think of any such *besides* documentation? 'Cause if
documentation is the only thing, then we should just call it
that. ;-)
:-) No, to be honest, I can't. But I'm not an expert - the Linux
distro people probably know a lot better than I do what types of files
give
On 11/20/2012 3:18 AM, Ronald Oussoren wrote:
Storing resource files outside of packages directories seems to be only
relevant for software that's packaged by a Linux distribution, not for python
packages installed into a virtualenv or on other platforms.
I would say this is the central
On 19.11.2012 23:46, PJ Eby wrote:
On Mon, Nov 19, 2012 at 2:37 PM, Paul Moore p.f.mo...@gmail.com wrote:
+1. But there's a third type of file, which is worth listing separately,
just to clarify:
* ??? files: constant files that are *not* typically used at runtime
(documentation, for example)
On Nov 20, 2012, at 09:18 AM, Ronald Oussoren wrote:
To be (too) snarky: because the FHS says so.
Less snarky, Linux distributors try to keep simular files together (for
example storing all gettext translations together in /usr/share/locale). To
play nice in such an enviroment Python packages
Bento uses these categories by default and lets you define your own. If
requested by the package, it writes the install-time prefixes to a
per-package .py file with NAME=value lines.
- prefix: install architecture-independent files
- eprefix: install architecture-dependent files
-
On Nov 20, 2012, at 04:51 PM, Daniel Holth wrote:
Bento uses these categories by default and lets you define your own. If
requested by the package, it writes the install-time prefixes to a
per-package .py file with NAME=value lines.
The key thing about the categories idea is that distro
On Tue, Nov 20, 2012 at 3:18 AM, Ronald Oussoren ronaldousso...@mac.comwrote:
On 19 Nov, 2012, at 20:26, PJ Eby p...@telecommunity.com wrote:
Data files should never be installed to package directories. But I'm
not aware of any good reason why resource files should ever be installed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/20/2012 10:21 PM, PJ Eby wrote:
On Tue, Nov 20, 2012 at 3:18 AM, Ronald Oussoren
ronaldousso...@mac.comwrote:
On 19 Nov, 2012, at 20:26, PJ Eby p...@telecommunity.com wrote:
Data files should never be installed to package
On Sun, Nov 18, 2012 at 6:40 PM, Vinay Sajip vinay_sa...@yahoo.co.ukwrote:
Chris McDonough chrism at plope.com writes:
That is not the definition of resource in setuptools-derived
systems. The definition of resource in setuptools-derived systems is
a non-Python file that lives in a
On 19 November 2012 19:26, PJ Eby p...@telecommunity.com wrote:
I think we should use some clearly-distinct (and mutually exclusive)
terminology going forward:
* Data files: stuff the user can and/or should change, such as
configuration files, startup databases, etc.
* Resource files:
On Mon, Nov 19, 2012 at 2:37 PM, Paul Moore p.f.mo...@gmail.com wrote:
On 19 November 2012 19:26, PJ Eby p...@telecommunity.com wrote:
I think we should use some clearly-distinct (and mutually exclusive)
terminology going forward:
* Data files: stuff the user can and/or should change, such
On 19 November 2012 21:46, PJ Eby p...@telecommunity.com wrote:
On Mon, Nov 19, 2012 at 2:37 PM, Paul Moore p.f.mo...@gmail.com wrote:
On 19 November 2012 19:26, PJ Eby p...@telecommunity.com wrote:
I think we should use some clearly-distinct (and mutually exclusive)
terminology going
Hey
I was reading this :
http://distlib.readthedocs.org/en/latest/overview.html#what-was-the-problem-with-packaging
and I thought I should bring up that distutils2 has implemented a way to
define data files that can be installed in the right places on the
target system. right here being
Tarek Ziadé tarek at ziade.org writes:
and I thought I should bring up that distutils2 has implemented a way to
define data files that can be installed in the right places on the
target system. right here being what the linux distros decides, or the
default win location etc.
There is a
On 11/18/12 10:15 PM, Vinay Sajip wrote:
Tarek Ziadé tarek at ziade.org writes:
and I thought I should bring up that distutils2 has implemented a way to
define data files that can be installed in the right places on the
target system. right here being what the linux distros decides, or the
Tarek Ziadé tarek at ziade.org writes:
Having a indirection like distutils2's resources allows the data files
to live alongside the code
in development and to be installed wherever that's desired by the
distro, without breaking
the code as long as it uses the indirection function to find
On 11/18/2012 05:08 PM, Vinay Sajip wrote:
Tarek Ziadé tarek at ziade.org writes:
Having a indirection like distutils2's resources allows the data files
to live alongside the code
in development and to be installed wherever that's desired by the
distro, without breaking
the code as long as it
Just come to my mind data test related to a package would be a natural
candidate:
mypack
|- __init__.py
|- test
|- __init__.py
|- test0.py
|- data
|- data.for.test0.dat
It is natural deploying them as part of an installer file.
I don't see why
On 11/18/12 11:15 PM, Chris McDonough wrote:
On 11/18/2012 05:08 PM, Vinay Sajip wrote:
Tarek Ziadé tarek at ziade.org writes:
Having a indirection like distutils2's resources allows the data files
to live alongside the code
in development and to be installed wherever that's desired by the
On 11/18/12 11:25 PM, Antonio Cavallo wrote:
Just come to my mind data test related to a package would be a natural
candidate:
mypack
|- __init__.py
|- test
|- __init__.py
|- test0.py
|- data
|- data.for.test0.dat
It is natural deploying them
On 11/18/2012 05:33 PM, Tarek Ziadé wrote:
On 11/18/12 11:15 PM, Chris McDonough wrote:
On 11/18/2012 05:08 PM, Vinay Sajip wrote:
Tarek Ziadé tarek at ziade.org writes:
Having a indirection like distutils2's resources allows the data files
to live alongside the code
in development and to be
On 11/18/12 11:45 PM, Chris McDonough wrote:
I don't really take exception to having such a feature (although I
would be unlikely to use it), but I do take exception to the first
paragraph of the description you pointed at:
This section describes the files used by the project which must not
On 11/18/2012 05:55 PM, Tarek Ziadé wrote:
On 11/18/12 11:45 PM, Chris McDonough wrote:
I don't really take exception to having such a feature (although I
would be unlikely to use it), but I do take exception to the first
paragraph of the description you pointed at:
This section describes the
25 matches
Mail list logo
