Re: f35-backgrounds ready for review

[Zbigniew Jędrzejewski-Szmek]

On Thu, Aug 26, 2021 at 02:45:18PM +0200, Miro Hrončok wrote:
>  On 26. 08. 21 14:40, Link Dupont wrote:
>  >Wouldn't a source package named 'fedora-backgrounds' work? 
Yes please!

>  >Each
>  >branch in dist-git would allow for new wallpapers each release. An
>  >RPM using the Fedora version as its version would result in an NVR
>  >that clearly identifies the wallpapers:
>  >
>  >* fedora-backgrounds/f34 => fedora-backgrounds-34-1.fc34
>  >* fedora-backgrounds/f35 => fedora-backgrounds-35-1.fc35
>  >* fedora-backgrounds/f35 => fedora-backgrounds-35-2.fc35
>  >
>  >But I must be missing something; this seems like its way too simple a solution.
>  
>  Nowadays, you can install e.g. f23-backgrounds on Fedora 34. If we
>  do it like you said, there would always be just one option.
>  
>  $ repoquery --repo=rawhide -a | egrep -- 'f[[:digit:]]+-backgrounds'
>  f21-backgrounds-0:21.1.0-13.fc35.noarch 
...
>  f34-backgrounds-xfce-0:34.0.1-2.fc35.noarch 
True. But those subpackages could just be built from one source package:

fedora-backgrounds/f34 => builds all subpackages in the range 21..34
fedora-backgrounds/f35 => builds all subpackages in the range 21..35
...

(This would likely mean that all fedora-backgrounds* source packages
would be imported into fedora-backgrounds and retired.)

Zbyszek

f35-backgrounds ready for review

[Link Dupont]

On Thu, Aug 26 2021 at 03:12:24 PM +0000, Zbigniew Jędrzejewski-Szmek 
<zbyszek(a)in.waw.pl&gt; wrote:
>  True. But those subpackages could just be built from one source 
>  package:
>  
>  fedora-backgrounds/f34 => builds all subpackages in the range 21..34
>  fedora-backgrounds/f35 => builds all subpackages in the range 21..35 
Assuming this range notation is a half-open interval, yes, I like this 
idea. Then each subsequent release could take the wallpapers from its 
predecessor and create a new subpackage named with the previous 
version. Would that get unwieldy as the spec file grows? Is there an 
opportunity for macros to make this more sustainable?

f35-backgrounds ready for review

[Zbigniew Jędrzejewski-Szmek]

On Thu, Aug 26, 2021 at 11:38:12AM -0400, Link Dupont wrote:
>  On Thu, Aug 26 2021 at 03:12:24 PM +0000, Zbigniew
>  Jędrzejewski-Szmek <zbyszek(a)in.waw.pl&gt; wrote:
>  >True. But those subpackages could just be built from one source
>  >package:
>  >
>  >fedora-backgrounds/f34 => builds all subpackages in the range 21..34
>  >fedora-backgrounds/f35 => builds all subpackages in the range 21..35
>  
>  Assuming this range notation is a half-open interval 
Closed on both sides, I think. But we actually have backgrounds for
earlier releases too, see below.

>  , yes, I like
>  this idea. Then each subsequent release could take the wallpapers
>  from its predecessor and create a new subpackage named with the
>  previous version. 
I think it'd look like this (e.g. f35 branch):

...
%package -n beefy-miracle-backgrounds
Summary: Backgrounds for f17
...
%package -n f21-backgrounds
Summary: Backgrounds for f21
...
%package -n f35-backgrounds
Summary: Backgrounds for f35
Provides: fedora-backgrounds    # only when f35 is the latest

and then for f36 this would be extended with:

%package -n f36-backgrounds
Summary: Backgrounds for f36
Provides: fedora-backgrounds    # moved here when f36 becomes the latest

>  Would that get unwieldy as the spec file grows? Is
>  there an opportunity for macros to make this more sustainable? 
I don't think it'd be much of a problem even in long form, because
we'd essentially get a bunch of new lines once for each release…
But yeah, some macro magic would probably make this nicer.

Zbyszek