On 28 December 2013 21:36, Vinay Sajip wrote:
> I don't have anything actually written, though all the information is
> available in the JSON for individual releases under the "source/data-files"
> key. I will look at writing a simple scanner which looks at all the unique
> directories declared
On 28 December 2013 06:17, Nick Coghlan wrote:
> The other main thing to look at in terms of current state of the art
> is npm, for both structure and hooks.
Another place to look would be existing usage in distributions on
PyPI. I know that Vinay has done some work on extracting build-time
data
On 28 December 2013 16:00, Nick Coghlan wrote:
> On 28 December 2013 06:02, Chris Barker wrote:
>> Then the python distro would map these to actual paths at install time: gnu
>> systems would map the gnu locations, Windows to Windows-appropriate
>> locations, OS-X to OS-X locations, etc This
On 28 December 2013 06:02, Chris Barker wrote:
> On Tue, Dec 24, 2013 at 2:28 PM, Nick Coghlan wrote:
>>
>> > But that concept doesn't work on all platforms, so we should be careful
>> > about isolating it.
>>
>> Encapsulating that assumption is why I think the "gnu" nesting is
>> justified. Ther
On Tue, Dec 24, 2013 at 2:28 PM, Nick Coghlan wrote:
> > But that concept doesn't work on all platforms, so we should be careful
> about isolating it.
>
> Encapsulating that assumption is why I think the "gnu" nesting is
> justified. There are layout expectations inherent in the autoconf director
On 27 December 2013 12:34, Marcus Smith wrote:
>>
>> data: directory for data files.
>>
>> This is still only a half-baked idea at this point, but I'm currently
>> leaning towards keeping the ".data" sysconfig subdirectories in
>> the wheel format cross platform (and somewhat Python specific),
>
>
> data: directory for data files.
>
> This is still only a half-baked idea at this point, but I'm currently
> leaning towards keeping the ".data" sysconfig subdirectories in
> the wheel format cross platform (and somewhat Python specific), and
> adding a new ".app" subdirectory in parallel.
On 25 Dec 2013 04:14, "Chris Barker" wrote:
>
> On Mon, Dec 23, 2013 at 1:43 PM, Daniel Holth > Agreed. My biggest
concern with this whole idea is that developers
>>
>> > (typically POSIX developers, but it applies equally to all) will
>> > *think* they need something like sbin because they are us
On Mon, Dec 23, 2013 at 1:43 PM, Daniel Holth > Agreed. My biggest concern
with this whole idea is that developers
> > (typically POSIX developers, but it applies equally to all) will
> > *think* they need something like sbin because they are used to the
> > concept from their environment, and so
On Mon, Dec 23, 2013 at 4:22 PM, Paul Moore wrote:
> On 23 December 2013 20:53, Chris Barker wrote:
>> then you explicitly put in "bin", sbin", "share", whatever?
>>
>> This seems really klunky to me, and also forces platform dependence, and is
>> fundamentally tied to how posix does things
>
On 23 December 2013 20:53, Chris Barker wrote:
> then you explicitly put in "bin", sbin", "share", whatever?
>
> This seems really klunky to me, and also forces platform dependence, and is
> fundamentally tied to how posix does things
>
> Maybe it's not possible, but I suggest that we could pr
On Sat, Dec 21, 2013 at 2:57 AM, Nick Coghlan wrote:
> compliant daemon like cobblerd as a wheel file - using Python specific
> formats to define the layout of full applications, not just libraries.
>
> I'd generally been resisting the idea of supporting this (since I
> favour interoperating wi
On 21 December 2013 22:01, Nick Coghlan wrote:
> On 21 December 2013 21:40, Paul Moore wrote:
>> On 21 December 2013 10:57, Nick Coghlan wrote:
>>> It's really the potential for FHS support that drives my interest in
>>> the idea, but if we're going to do something like this at all, it
>>> shoul
On 21 December 2013 21:40, Paul Moore wrote:
> On 21 December 2013 10:57, Nick Coghlan wrote:
>> And these are the generic directories that aren't necessarily Python
>> specific:
>>
>> scripts: directory for script files.
>> data: directory for data files.
>
> It's worth noting that "dat
On 21 December 2013 10:57, Nick Coghlan wrote:
> And these are the generic directories that aren't necessarily Python specific:
>
> scripts: directory for script files.
> data: directory for data files.
It's worth noting that "data", although in essence a platform neutral
term, is in prac
With the Python 3.4 feature freeze behind us, I've started looking at
doing a new update of the draft metadata 2.0 docs. Vaguely related to
that are the recent discussions about being able to publish an FHS
compliant daemon like cobblerd as a wheel file - using Python specific
formats to define the
16 matches
Mail list logo
