On 18 November 2015 at 02:29, Jason L Tibbitts III wrote:
>> "NC" == Nick Coghlan writes:
>
> NC> If so, then there's some relevant work currently under way upstream
> NC> to improve the interaction between Python installation tools and
> NC> build systems to improve the metadata extraction p
On Nov 17, 2015 8:18 AM, "Neal Gompa" wrote:
>
> I see the problem you are describing, but how do you solve it currently?
>
Currently we use manually specified dependencies with package names here.
So when python2.6-foo is built, the packager specifies a dependency on
python2.6-setuptools.
> That
> "NC" == Nick Coghlan writes:
NC> If so, then there's some relevant work currently under way upstream
NC> to improve the interaction between Python installation tools and
NC> build systems to improve the metadata extraction process, rather
NC> than relying on implementation details of setupt
On Tue, Nov 17, 2015 at 10:43 AM, Toshio Kuratomi wrote:
>
> On Nov 17, 2015 6:47 AM, "Neal Gompa" wrote:
>>
>> That's already guaranteed by the auto-generated python(abi) requires,
>> and that would also make it hugely problematic to use in spec files in
>> any distro agnostic manner, so I don't
On Nov 17, 2015 6:47 AM, "Neal Gompa" wrote:
>
> On Tue, Nov 17, 2015 at 9:44 AM, Toshio Kuratomi
wrote:
> > One thing I would change, though: instead of python2dist(name) use
> > python2.7dist(name). A module built for python 2.7 won't be able to
import
> > a module built for python2.6 (the pyt
> On Nov 17, 2015, at 9:53 AM, Neal Gompa wrote:
>
> On Tue, Nov 17, 2015 at 9:35 AM, Donald Stufft wrote:
>>
>>> On Nov 17, 2015, at 9:26 AM, Neal Gompa wrote:
>>>
>>> The dependency generator uses pkg_resources (specifically
>>> Distribution, FileMetadata, PathMetadata) to read data in the
On Tue, Nov 17, 2015 at 9:35 AM, Donald Stufft wrote:
>
>> On Nov 17, 2015, at 9:26 AM, Neal Gompa wrote:
>>
>> The dependency generator uses pkg_resources (specifically
>> Distribution, FileMetadata, PathMetadata) to read data in the
>> .egg-info directory. That should still work with .dist-info
On Nov 17, 2015 6:06 AM, "Nick Coghlan" wrote:
>
> On 17 November 2015 at 23:25, Neal Gompa wrote:
> > As for naming, I'm all ears for a better name, because if the "egg"
> > name is going away, I'd rather it not continue to say that.
>
> My suggestions would be either:
>
> python2dist(name)/
On Tue, Nov 17, 2015 at 9:44 AM, Toshio Kuratomi wrote:
>
> On Nov 17, 2015 6:06 AM, "Nick Coghlan" wrote:
>>
>> On 17 November 2015 at 23:25, Neal Gompa wrote:
>> > As for naming, I'm all ears for a better name, because if the "egg"
>> > name is going away, I'd rather it not continue to say tha
> On Nov 17, 2015, at 9:26 AM, Neal Gompa wrote:
>
> On Tue, Nov 17, 2015 at 8:34 AM, Donald Stufft wrote:
>>
>>> On Nov 17, 2015, at 8:25 AM, Neal Gompa wrote:
>>> Is the format inside of the .dist-info directory the same as the older
>>> .egg-info and .egg-link directories? If so, it should
On Tue, Nov 17, 2015 at 8:34 AM, Donald Stufft wrote:
>
>> On Nov 17, 2015, at 8:25 AM, Neal Gompa wrote:
>> Is the format inside of the .dist-info directory the same as the older
>> .egg-info and .egg-link directories? If so, it should be easy to add
>> to read that information too.
>
> Currentl
On 17 November 2015 at 23:25, Neal Gompa wrote:
> As for naming, I'm all ears for a better name, because if the "egg"
> name is going away, I'd rather it not continue to say that.
My suggestions would be either:
python2dist(name)/python3dist(name)
or:
python2(name)/python3(name)
The "
> On Nov 17, 2015, at 8:25 AM, Neal Gompa wrote:
>
> On Tue, Nov 17, 2015 at 8:05 AM, Donald Stufft wrote:
>>
>>> On Nov 17, 2015, at 7:54 AM, Nick Coghlan wrote:
>>>
>>> On 17 November 2015 at 22:05, Neal Gompa wrote:
and
I wanted to give the Python SIG in Fedora the opportunity
On Tue, Nov 17, 2015 at 8:05 AM, Donald Stufft wrote:
>
>> On Nov 17, 2015, at 7:54 AM, Nick Coghlan wrote:
>>
>> On 17 November 2015 at 22:05, Neal Gompa wrote:
>>> and
>>> I wanted to give the Python SIG in Fedora the opportunity to try it
>>> out and see if we might want to enable it in Fedor
> On Nov 17, 2015, at 7:54 AM, Nick Coghlan wrote:
>
> On 17 November 2015 at 22:05, Neal Gompa wrote:
>> On Tue, Nov 17, 2015 at 3:26 AM, Nick Coghlan wrote:
>>> I'm not clear on what you mean by depending on an egg. Eggs are a
>>> binary format that isn't compatible with Linux distro packagi
On 17 November 2015 at 22:05, Neal Gompa wrote:
> On Tue, Nov 17, 2015 at 3:26 AM, Nick Coghlan wrote:
>> I'm not clear on what you mean by depending on an egg. Eggs are a
>> binary format that isn't compatible with Linux distro packaging
>> policies, since they lose too much structural informati
On Tue, Nov 17, 2015 at 3:26 AM, Nick Coghlan wrote:
> I'm not clear on what you mean by depending on an egg. Eggs are a
> binary format that isn't compatible with Linux distro packaging
> policies, since they lose too much structural information regarding
> where files should be installed for pol
On 17 November 2015 at 00:38, Neal Gompa wrote:
> Hello all,
>
> I recently upstreamed some fixes to a new RPM dependency generator
> that will be available as an option for distributions to enable. The
> new generator uses python .egg data to generate Provides and Requires
> in the form of python
18 matches
Mail list logo
