On Tuesday, January 19, 2021 8:50:38 PM CET Dan Čermák wrote:
> Dominik 'Rathann' Mierzejewski writes:
>
> > On Monday, 18 January 2021 at 23:29, Dan Čermák wrote:
> >> clime writes:
> > [...]
> >> > But when you said "workaround", I was thinking that you actually saw
> >> > the correct solution
On Tue, Jan 19, 2021 at 2:51 PM Dan Čermák
wrote:
>
> Dominik 'Rathann' Mierzejewski writes:
>
> > On Monday, 18 January 2021 at 23:29, Dan Čermák wrote:
> >> clime writes:
> > [...]
> >> > But when you said "workaround", I was thinking that you actually saw
> >> > the correct solution because "
Dominik 'Rathann' Mierzejewski writes:
> On Monday, 18 January 2021 at 23:29, Dan Čermák wrote:
>> clime writes:
> [...]
>> > But when you said "workaround", I was thinking that you actually saw
>> > the correct solution because "workaround" is imho used usually when
>> > someone can't or don't
On Monday, 18 January 2021 at 23:29, Dan Čermák wrote:
> clime writes:
[...]
> > But when you said "workaround", I was thinking that you actually saw
> > the correct solution because "workaround" is imho used usually when
> > someone can't or don't want to solve things the right way so he/she
> >
clime writes:
> On Mon, 4 Jan 2021 at 20:43, Dan Čermák
> wrote:
>>
>> clime writes:
>>
>> > ...snip...
>> >> >
>> >> > $ preproc-rpmspec pkg.spec.rpkg # prints rendered spec to stdout,
>> >> > pkg.spec.rpkg is a spec template
>> >>
>> >> This would be a viable workaround, but a workaround ne
...snip...
Btw. I posted a long comment here: https://pagure.io/fesco/issue/2532
basically trying to explain the proposal more and mention the
use-cases where it would be useful. So, please, read if you are
interested. I guess, if there is a further discussion it should be
probably carried out her
On Mon, 4 Jan 2021 at 20:43, Dan Čermák wrote:
>
> clime writes:
>
> > ...snip...
> >> >
> >> > $ preproc-rpmspec pkg.spec.rpkg # prints rendered spec to stdout,
> >> > pkg.spec.rpkg is a spec template
> >>
> >> This would be a viable workaround, but a workaround nevertheless. Since
> >> I am no
clime writes:
> ...snip...
>> >
>> > $ preproc-rpmspec pkg.spec.rpkg # prints rendered spec to stdout,
>> > pkg.spec.rpkg is a spec template
>>
>> This would be a viable workaround, but a workaround nevertheless. Since
>> I am not frequently rebuilding Fedora rpms outside of mock, koji & copr,
>
On Thu, Dec 17, 2020 at 09:14:40PM +0100, Fabio Valentini wrote:
> On Thu, Dec 17, 2020 at 8:06 PM Ben Cotton wrote:
> >
> > https://fedoraproject.org/wiki/Changes/Enable_Spec_File_Preprocessing
> >
> >
> > == Summary ==
> > This change should enable an opt-in spec file preprocessor in Fedora
> >
...snip...
> >
> > $ preproc-rpmspec pkg.spec.rpkg # prints rendered spec to stdout,
> > pkg.spec.rpkg is a spec template
>
> This would be a viable workaround, but a workaround nevertheless. Since
> I am not frequently rebuilding Fedora rpms outside of mock, koji & copr,
> I cannot tell how much
clime writes:
> On Sat, 19 Dec 2020 at 20:07, Dan Čermák
> wrote:
>>
>> clime writes:
>>
>> > On Thu, 17 Dec 2020 at 22:04, James Szinger wrote:
>> >>
>> >> On Thu, 17 Dec 2020 14:05:40 -0500
>> >> Ben Cotton wrote:
>> >>
>> >> 1. How does this affect users who download, maybe modify, and re
Adam Williamson writes:
> On Sat, 2020-12-19 at 20:07 +0100, Dan Čermák wrote:
>> clime writes:
>>
>> > On Thu, 17 Dec 2020 at 22:04, James Szinger wrote:
>> > >
>> > > On Thu, 17 Dec 2020 14:05:40 -0500
>> > > Ben Cotton wrote:
>> > >
>> > > 1. How does this affect users who download, mayb
On Fri, 18 Dec 2020 at 17:03, clime wrote:
>
> On Fri, 18 Dec 2020 at 16:23, James Szinger wrote:
> >
> > On Fri, 18 Dec 2020 00:51:49 +0100
> > clime wrote:
> >
> > > Well, the users here are still packagers here no? I thought the "User"
> > > in the title means "end user" who shouldn't be affe
On 21. 12. 20 2:38, clime wrote:
On Sun, 20 Dec 2020 at 11:39, Miro Hrončok wrote:
On 12/20/20 1:38 AM, clime wrote:
I view this proposal as a risk that the spec files will look a bit more
weird, and the spec files maintenance will start diverging too much.
Everything happening for an overesti
On Sun, 20 Dec 2020 at 11:39, Miro Hrončok wrote:
>
> On 12/20/20 1:38 AM, clime wrote:
> >> I view this proposal as a risk that the spec files will look a bit more
> >> weird, and the spec files maintenance will start diverging too much.
> >> Everything happening for an overestimated triviality a
On 12/20/20 1:38 AM, clime wrote:
I view this proposal as a risk that the spec files will look a bit more
weird, and the spec files maintenance will start diverging too much.
Everything happening for an overestimated triviality as IMO
the release/changelog is [1].
Well, even if this change is ac
On Sun, 20 Dec 2020 at 00:23, Pavel Raiskup wrote:
>
> On Thursday, December 17, 2020 8:05:40 PM CET Ben Cotton wrote:
> > https://fedoraproject.org/wiki/Changes/Enable_Spec_File_Preprocessing
> >
> > == Summary ==
> > This change should enable an opt-in spec file preprocessor in Fedora
> > infras
On Thursday, December 17, 2020 8:05:40 PM CET Ben Cotton wrote:
> https://fedoraproject.org/wiki/Changes/Enable_Spec_File_Preprocessing
>
> == Summary ==
> This change should enable an opt-in spec file preprocessor in Fedora
> infrastructure for the benefit of packagers. The preprocessor allows
>
On Sat, 19 Dec 2020 at 20:57, clime wrote:
>
> On Sat, 19 Dec 2020 at 20:07, Dan Čermák
> wrote:
> >
> > clime writes:
> >
> > > On Thu, 17 Dec 2020 at 22:04, James Szinger wrote:
> > >>
> > >> On Thu, 17 Dec 2020 14:05:40 -0500
> > >> Ben Cotton wrote:
> > >>
> > >> 1. How does this affect u
On Sat, 19 Dec 2020 at 20:07, Dan Čermák wrote:
>
> clime writes:
>
> > On Thu, 17 Dec 2020 at 22:04, James Szinger wrote:
> >>
> >> On Thu, 17 Dec 2020 14:05:40 -0500
> >> Ben Cotton wrote:
> >>
> >> 1. How does this affect users who download, maybe modify, and rebuild
> >> the SRPM? Can they
On Sat, Dec 19, 2020 at 2:21 PM Adam Williamson
wrote:
>
> On Sat, 2020-12-19 at 20:07 +0100, Dan Čermák wrote:
> > clime writes:
> >
> > > On Thu, 17 Dec 2020 at 22:04, James Szinger wrote:
> > > >
> > > > On Thu, 17 Dec 2020 14:05:40 -0500
> > > > Ben Cotton wrote:
> > > >
> > > > 1. How does
On Sat, 2020-12-19 at 20:07 +0100, Dan Čermák wrote:
> clime writes:
>
> > On Thu, 17 Dec 2020 at 22:04, James Szinger wrote:
> > >
> > > On Thu, 17 Dec 2020 14:05:40 -0500
> > > Ben Cotton wrote:
> > >
> > > 1. How does this affect users who download, maybe modify, and rebuild
> > > the SRPM
clime writes:
> On Thu, 17 Dec 2020 at 22:04, James Szinger wrote:
>>
>> On Thu, 17 Dec 2020 14:05:40 -0500
>> Ben Cotton wrote:
>>
>> 1. How does this affect users who download, maybe modify, and rebuild
>> the SRPM? Can they continue to use rpmbuid and mock as they have
>> been? Does the SR
On Sat, 19 Dec 2020 at 03:02, Luya Tshimbalanga wrote:
>
>
> On 2020-12-18 11:13 a.m., Robbie Harwood wrote:
> > clime writes:
> >
> >> On Fri, 18 Dec 2020 at 18:20, Robbie Harwood wrote:
> >>> Robert-André Mauchin writes:
> >>>
> On 12/18/20 3:52 PM, James Szinger wrote:
> > No. One
On 2020-12-18 11:13 a.m., Robbie Harwood wrote:
clime writes:
On Fri, 18 Dec 2020 at 18:20, Robbie Harwood wrote:
Robert-André Mauchin writes:
On 12/18/20 3:52 PM, James Szinger wrote:
No. One can also download the sources from upstream using spectool or
similar, even wget or curl. My
clime writes:
> On Fri, 18 Dec 2020 at 18:20, Robbie Harwood wrote:
>>
>> Robert-André Mauchin writes:
>>
>> > On 12/18/20 3:52 PM, James Szinger wrote:
>> >>
>> >> No. One can also download the sources from upstream using spectool or
>> >> similar, even wget or curl. My local work flow is ty
On Fri, 18 Dec 2020 at 18:20, Robbie Harwood wrote:
>
> Robert-André Mauchin writes:
>
> > On 12/18/20 3:52 PM, James Szinger wrote:
> >>
> >> No. One can also download the sources from upstream using spectool or
> >> similar, even wget or curl. My local work flow is typically get or
> >> creat
Robert-André Mauchin writes:
> On 12/18/20 3:52 PM, James Szinger wrote:
>>
>> No. One can also download the sources from upstream using spectool or
>> similar, even wget or curl. My local work flow is typically get or
>> create spec file and patches, spectool -g, rpmbuild -bs, mock.
>>
>
> U
Hello,
On Fri, Dec 18, 2020 at 5:53 PM Robert-André Mauchin wrote:
>
> On 12/18/20 3:52 PM, James Szinger wrote:
> >
> > No. One can also download the sources from upstream using spectool or
> > similar, even wget or curl. My local work flow is typically get or
> > create spec file and patches,
On 12/18/20 3:52 PM, James Szinger wrote:
No. One can also download the sources from upstream using spectool or
similar, even wget or curl. My local work flow is typically get or
create spec file and patches, spectool -g, rpmbuild -bs, mock.
Unrelated to the topic at hand, but why do people
On Fri, 18 Dec 2020 at 15:53, James Szinger wrote:
>
> On Fri, 18 Dec 2020 03:04:01 +0100
> clime wrote:
>
> > I wouldn't call it "deprecating rpmbuild". That's certainly not at all
> > my intention.
> >
> > As a side-point, I think the cases where bare rpmbuild is used to
> > build an rpm/srpm f
On Fri, 18 Dec 2020 at 16:23, James Szinger wrote:
>
> On Fri, 18 Dec 2020 00:51:49 +0100
> clime wrote:
>
> > Well, the users here are still packagers here no? I thought the "User"
> > in the title means "end user" who shouldn't be affected by it. Maybe
> > Ben can clarify this.
>
> I am making
On Fri, 18 Dec 2020 00:51:49 +0100
clime wrote:
> Well, the users here are still packagers here no? I thought the "User"
> in the title means "end user" who shouldn't be affected by it. Maybe
> Ben can clarify this.
I am making a distinction between Fedora packagers who use the Fedora
infrastruc
On Fri, 18 Dec 2020 03:04:01 +0100
clime wrote:
> I wouldn't call it "deprecating rpmbuild". That's certainly not at all
> my intention.
>
> As a side-point, I think the cases where bare rpmbuild is used to
> build an rpm/srpm from a dist-git repo are rather limited because you
> probably need t
Dne pá 18. 12. 2020 10:52 dop. uživatel Miro Hrončok
napsal:
> On 12/18/20 1:19 AM, clime wrote:
> >> I'd very much like to understand the impact of this on the following:
> >>
> >>
> >> 1) Provenpackagers doing mass spec changes/updates.
> > If the mass spec change/update doesn't involve an rpkg
On 12/18/20 12:57 AM, Matthew Miller wrote:
On Fri, Dec 18, 2020 at 12:24:10AM +0100, clime wrote:
It would be possible to specify the spec template as an rpm Source so
it would get included into the resulting srpm as well.
Yeah I was thinking the spec file templating system could automaticall
On 12/18/20 1:19 AM, clime wrote:
I'd very much like to understand the impact of this on the following:
1) Provenpackagers doing mass spec changes/updates.
If the mass spec change/update doesn't involve an rpkg macro, then
there is no difference.
I don't understand how there is no difference
On Friday, 18 December 2020, Tom Stellard wrote:
> On 12/17/20 11:05 AM, Ben Cotton wrote:
>
>> https://fedoraproject.org/wiki/Changes/Enable_Spec_File_Preprocessing
>>
>>
>> == Summary ==
>> This change should enable an opt-in spec file preprocessor in Fedora
>> infrastructure for the benefit of
On 12/17/20 11:05 AM, Ben Cotton wrote:
https://fedoraproject.org/wiki/Changes/Enable_Spec_File_Preprocessing
== Summary ==
This change should enable an opt-in spec file preprocessor in Fedora
infrastructure for the benefit of packagers. The preprocessor allows
some very neat tricks that were i
On Fri, 18 Dec 2020 at 02:27, Japheth Cleaver wrote:
>
> On 12/17/2020 3:59 PM, Matthew Miller wrote:
>
> On Fri, Dec 18, 2020 at 12:51:49AM +0100, clime wrote:
>
> This change proposal does affect users. The User Experience section
> needs to answer the following:
>
> Well, the users here are st
On 12/17/2020 3:59 PM, Matthew Miller wrote:
On Fri, Dec 18, 2020 at 12:51:49AM +0100, clime wrote:
This change proposal does affect users. The User Experience section
needs to answer the following:
Well, the users here are still packagers here no? I thought the "User"
in the title means "end
On Fri, 18 Dec 2020 at 00:58, Matthew Miller wrote:
>
> On Fri, Dec 18, 2020 at 12:24:10AM +0100, clime wrote:
> > It would be possible to specify the spec template as an rpm Source so
> > it would get included into the resulting srpm as well.
>
> Yeah I was thinking the spec file templating syste
On Thu, 17 Dec 2020 at 21:23, Miro Hrončok wrote:
>
> On 12/17/20 8:05 PM, Ben Cotton wrote:
> > https://fedoraproject.org/wiki/Changes/Enable_Spec_File_Preprocessing
> >
> >
> > == Summary ==
> > This change should enable an opt-in spec file preprocessor in Fedora
> > infrastructure for the benef
On Fri, Dec 18, 2020 at 12:51:49AM +0100, clime wrote:
> > This change proposal does affect users. The User Experience section
> > needs to answer the following:
> Well, the users here are still packagers here no? I thought the "User"
> in the title means "end user" who shouldn't be affected by it
On Fri, Dec 18, 2020 at 12:24:10AM +0100, clime wrote:
> It would be possible to specify the spec template as an rpm Source so
> it would get included into the resulting srpm as well.
Yeah I was thinking the spec file templating system could automatically add
the original spec as Source where
On Thu, 17 Dec 2020 at 22:04, James Szinger wrote:
>
> On Thu, 17 Dec 2020 14:05:40 -0500
> Ben Cotton wrote:
>
> > https://fedoraproject.org/wiki/Changes/Enable_Spec_File_Preprocessing
> >
> > == Summary ==
> > This change should enable an opt-in spec file preprocessor in Fedora
> > infrastructu
On Thu, 17 Dec 2020 at 21:34, James Cassell wrote:
>
>
> On Thu, Dec 17, 2020, at 2:05 PM, Ben Cotton wrote:
> > https://fedoraproject.org/wiki/Changes/Enable_Spec_File_Preprocessing
> >
> >
> > == Summary ==
> > This change should enable an opt-in spec file preprocessor in Fedora
> > infrastructu
...snip...
>
> I'm generally not excited about this, as it adds a huge layer of
> indirection and a ton of extra magic that makes it harder to decipher
> what is happening.
>
I don't think there is any magic in it. Everything is clearly
documented and every expansion clearly defined and also intu
On Thu, 17 Dec 2020 at 21:15, Fabio Valentini wrote:
>
> On Thu, Dec 17, 2020 at 8:06 PM Ben Cotton wrote:
> >
> > https://fedoraproject.org/wiki/Changes/Enable_Spec_File_Preprocessing
> >
> >
> > == Summary ==
> > This change should enable an opt-in spec file preprocessor in Fedora
> > infrastru
On 12/17/20 9:21 PM, Miro Hrončok wrote:
On 12/17/20 8:05 PM, Ben Cotton wrote:
https://fedoraproject.org/wiki/Changes/Enable_Spec_File_Preprocessing
== Summary ==
This change should enable an opt-in spec file preprocessor in Fedora
infrastructure for the benefit of packagers. The preprocess
On Thu, 17 Dec 2020 14:05:40 -0500
Ben Cotton wrote:
> https://fedoraproject.org/wiki/Changes/Enable_Spec_File_Preprocessing
>
> == Summary ==
> This change should enable an opt-in spec file preprocessor in Fedora
> infrastructure for the benefit of packagers. The preprocessor allows
> some very
On Thu, Dec 17, 2020, at 2:05 PM, Ben Cotton wrote:
> https://fedoraproject.org/wiki/Changes/Enable_Spec_File_Preprocessing
>
>
> == Summary ==
> This change should enable an opt-in spec file preprocessor in Fedora
> infrastructure for the benefit of packagers. The preprocessor allows
> some ver
On 12/17/20 8:05 PM, Ben Cotton wrote:
https://fedoraproject.org/wiki/Changes/Enable_Spec_File_Preprocessing
== Summary ==
This change should enable an opt-in spec file preprocessor in Fedora
infrastructure for the benefit of packagers. The preprocessor allows
some very neat tricks that were im
On Thu, Dec 17, 2020 at 3:15 PM Fabio Valentini wrote:
>
> On Thu, Dec 17, 2020 at 8:06 PM Ben Cotton wrote:
> >
> > https://fedoraproject.org/wiki/Changes/Enable_Spec_File_Preprocessing
> >
> >
> > == Summary ==
> > This change should enable an opt-in spec file preprocessor in Fedora
> > infrast
On Thu, Dec 17, 2020 at 8:06 PM Ben Cotton wrote:
>
> https://fedoraproject.org/wiki/Changes/Enable_Spec_File_Preprocessing
>
>
> == Summary ==
> This change should enable an opt-in spec file preprocessor in Fedora
> infrastructure for the benefit of packagers. The preprocessor allows
> some very
https://fedoraproject.org/wiki/Changes/Enable_Spec_File_Preprocessing
== Summary ==
This change should enable an opt-in spec file preprocessor in Fedora
infrastructure for the benefit of packagers. The preprocessor allows
some very neat tricks that were impossible before, for example
generate cha
56 matches
Mail list logo
