-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
> wrote:
>
>>
>> On 19 Nov, 2012, at 20:26, PJ Eby wrote:
>>>
>>>
>>> Data files should never be installed to package directories. But
>>> I'm
>> not aware o
On Tue, Nov 20, 2012 at 3:18 AM, Ronald Oussoren wrote:
>
> On 19 Nov, 2012, at 20:26, PJ Eby 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) snar
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 main
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
- bindi
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 packa
On 19.11.2012 23:46, PJ Eby wrote:
On Mon, Nov 19, 2012 at 2:37 PM, Paul Moore 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)
Maybe "support fi
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 p
Daniel Holth gmail.com> writes:
[referring to "Provides-Dist"]
> Mostly it seems a bit silly to have so much conversations about parts of the
> pep that remain unchanged from previously accepted versions...
I don't agree with the suggestion that we shouldn't discuss it because it was
accepted in
On Tue, Nov 20, 2012 at 01:30:43PM +0100, Edward Ekelund wrote:
>
> Hi,
>
> I'm wondering if there is a way to generate two .deb-files from a single
> setup.py file. Or, if that's not possible, generate deb files from
> custom-named setup.py files, e.g. client_setup.py & server_setup.py.
You can
Hi,
I'm wondering if there is a way to generate two .deb-files from a single
setup.py file. Or, if that's not possible, generate deb files from
custom-named setup.py files, e.g. client_setup.py & server_setup.py.
The reason I'm asking is that I need the source code to reside in the
same root fo
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 them
On 19 Nov, 2012, at 20:26, PJ Eby 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, Linux distributors tr
12 matches
Mail list logo
