On Fri, Jul 10, 2009 at 8:17 PM, P.J. Eby wrote:
> At 03:31 PM 7/10/2009 +0200, Tarek Ziadé wrote:
>>
>> On Thu, Jul 9, 2009 at 9:09 PM, P.J. Eby wrote:
>> > At 02:46 PM 7/9/2009 -0400, Tres Seaver wrote:
>> >>
>> >> -BEGIN PGP SIGNED MESSAGE-
>> >> Hash: SHA1
>> >>
>> >> Nick Coghlan wrote
At 03:31 PM 7/10/2009 +0200, Tarek Ziadé wrote:
On Thu, Jul 9, 2009 at 9:09 PM, P.J. Eby wrote:
> At 02:46 PM 7/9/2009 -0400, Tres Seaver wrote:
>>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Nick Coghlan wrote:
>> > P.J. Eby wrote:
>> >>> Also,
>> >>> why should the RECORD file be
-On [20090710 15:32], Tarek Ziadé (ziade.ta...@gmail.com) wrote:
>setup(
>...
>data_files={'i18n': ['en.po', 'fr.po']},
>extra_prefixes={'i18n': {'unix_prefix': '/somewhere',
> 'mac': '/Application/right/here'}
> ...
> )
As an aside:
Where i18n
On Thu, Jul 9, 2009 at 9:09 PM, P.J. Eby wrote:
> At 02:46 PM 7/9/2009 -0400, Tres Seaver wrote:
>>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Nick Coghlan wrote:
>> > P.J. Eby wrote:
>> >>> Also,
>> >>> why should the RECORD file be generated at all by bdist* commands?
>> >> bdist
David Lyon wrote:
> All it requires is a few word changes to the documentation to tell
> programmers to put your documentation in "docs"...
There is no current distutils setting to indicate that a particular data
file is actually documentation rather than something else - hence such a
thing *isn't
On Thu, 09 Jul 2009 16:00:41 -0400, Fred Drake wrote:
> At 02:46 PM 7/9/2009 -0400, Tres Seaver wrote:
>> - - docs
>> - - i18n / locales
>
>
> On Jul 9, 2009, at 3:09 PM, P.J. Eby wrote:
>> Unfortunately, the distutils don't currently have a way to specify
>> these.
>
>
> There actually is a
On Fri, 10 Jul 2009 05:53:13 +1000, Nick Coghlan
wrote:
> There are probably all sorts of other useful distinctions which could be
> made. However, that would be a topic for a different PEP - as Tarek
> pointed out, improving distutils is such a huge can of worms that trying
> to tackle all the is
At 02:46 PM 7/9/2009 -0400, Tres Seaver wrote:
- - docs
- - i18n / locales
On Jul 9, 2009, at 3:09 PM, P.J. Eby wrote:
Unfortunately, the distutils don't currently have a way to specify
these.
There actually is a way to identify documentation files via setup.cfg,
but I don't know if the
Tres Seaver wrote:
> Nick Coghlan wrote:
>> The question then would be whether relative paths should be handled
>> directly in the RECORD file (as in the current PEP) or by writing a "."
>> into PREFIXES to indicate relative paths.
>
> Per discussion with Matthias Klose, it would be useful to spli
At 02:46 PM 7/9/2009 -0400, Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nick Coghlan wrote:
> P.J. Eby wrote:
>>> Also,
>>> why should the RECORD file be generated at all by bdist* commands?
>> bdist commands that use "install --root" will get it as a side effect,
>> so the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nick Coghlan wrote:
> P.J. Eby wrote:
>>> Also,
>>> why should the RECORD file be generated at all by bdist* commands?
>> bdist commands that use "install --root" will get it as a side effect,
>> so they don't have to do anything special. They needn'
P.J. Eby wrote:
>> Also,
>> why should the RECORD file be generated at all by bdist* commands?
>
> bdist commands that use "install --root" will get it as a side effect,
> so they don't have to do anything special. They needn't even generate
> the PREFIXES, if PREFIXES is also generated by "inst
At 06:51 PM 7/8/2009 -0700, Sridhar Ratnakumar wrote:
Is there any reason why RECORD file can't be generated at runtime?
Applications can be relocatable, yet require plugins and libraries to
be upgraded, installed, uninstalled, etc.
(Also, RECORD is cross-platform to allow cross-platform
in
Is there any reason why RECORD file can't be generated at runtime? Also,
why should the RECORD file be generated at all by bdist* commands?
A .deb file contains "data.tar.gz" that is simply extracted over "/".
There is no need for RECORD inside a .deb file because it is implicit in
the cont
Just an idea... suppose that instead of using "real" absolute paths
in the RECORD file for non-local files (scripts, data, etc) we
changed the format to include a "prefix" field, containing something
like LIBDIR, SHARE, SCRIPTS, etc., ala bdist_wininst internals?
Also, we could include a sepa
15 matches
Mail list logo
