On Thu, Oct 29, 2015 at 10:48 PM, Petr Pisar wrote:
> However, I have to admit, that having a standard package name for macros
> needed for building non-native-extenstion (noarch) binary packages can
> be handy. Especially if major of packages do not need header files and
> compiler, so depending
On 2015-10-29, Dominik 'Rathann' Mierzejewski wrote:
> On Thursday, 29 October 2015 at 01:31, Christopher Meng wrote:
>> On Thu, Oct 29, 2015 at 3:16 AM, Tom Hughes wrote:
>> >
>> > On 28/10/15 19:12, Mike Bonnet wrote:
>> >>
>> >> https://fedoraproject.org/wiki/Packaging:Python#BuildRequires
>>
On 29/10/15 11:34, Dominik 'Rathann' Mierzejewski wrote:
On Thursday, 29 October 2015 at 01:31, Christopher Meng wrote:
Not my first time hitting on missing macros just because lack of
pythonN-devel, but if you just extract them from pythonN-devel to package
similar to these packages below, I r
On Thursday, 29 October 2015 at 01:31, Christopher Meng wrote:
> On Thu, Oct 29, 2015 at 3:16 AM, Tom Hughes wrote:
> >
> > On 28/10/15 19:12, Mike Bonnet wrote:
> >>
> >> https://fedoraproject.org/wiki/Packaging:Python#BuildRequires
> >>
> >> This is *not* required for pure Python packages, only
On Thu, Oct 29, 2015 at 3:16 AM, Tom Hughes wrote:
>
> On 28/10/15 19:12, Mike Bonnet wrote:
>>
>> https://fedoraproject.org/wiki/Packaging:Python#BuildRequires
>>
>> This is *not* required for pure Python packages, only for packages
>> compiling native extensions:
>
>
> Are you sure? Don't you ne
I also sent a notice to Fedora's python list, pinged the relevant IRC
channel and have generally tried to let people know about this. The
actual macros are in the pagure repo but there's still more work to be
done. https://pagure.io/python-macros
- J<
--
devel mailing list
devel@lists.fedorapr
On 10/28/15 12:30 PM, Jason L Tibbitts III wrote:
"MB" == Mike Bonnet writes:
MB> That sounds like a good plan. Is this work being tracked anywhere?
As you might expect, in an FPC ticket:
https://fedorahosted.org/fpc/ticket/567
Thanks! I'll follow along there.
--
devel mailing list
devel
> "MB" == Mike Bonnet writes:
MB> That sounds like a good plan. Is this work being tracked anywhere?
As you might expect, in an FPC ticket:
https://fedorahosted.org/fpc/ticket/567
- J<
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/de
On 10/28/15 12:21 PM, Jason L Tibbitts III wrote:
Luckily I saw this. The best way to make sure the packaging committee
sees this kind of thing is to open a ticket at
https://fedorahosted.org/fpc/
However, I don't believe your assertion to be true. python*-devel is
the package with the depende
Luckily I saw this. The best way to make sure the packaging committee
sees this kind of thing is to open a ticket at
https://fedorahosted.org/fpc/
However, I don't believe your assertion to be true. python*-devel is
the package with the dependency on the RPM macros; if you depend only on
python
On 28/10/15 19:12, Mike Bonnet wrote:
https://fedoraproject.org/wiki/Packaging:Python#BuildRequires
This is *not* required for pure Python packages, only for packages
compiling native extensions:
Are you sure? Don't you need them for the RPM macros they contain?
Tom
--
Tom Hughes (t...@comp
https://fedoraproject.org/wiki/Packaging:Python#BuildRequires
This is *not* required for pure Python packages, only for packages
compiling native extensions:
http://koji.fedoraproject.org/koji/rpminfo?rpmID=6908337
Can we change this guideline to say packages should:
BuildRequires: python2
12 matches
Mail list logo
