On Fri, Aug 27, 2021 at 9:12 AM Zbigniew Jędrzejewski-Szmek < zbys...@in.waw.pl> wrote:
> 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 <zbys...@in.waw.pl> 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 > > Currently, the spec file has subpackages for each desktop environment though (e.g. f35-backgrounds-gnome, f35-backgrounds-kde, etc.) since they have to be installed in different places for each background. How would we handle that in this type of spec file organization? -Ian > > 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 > _______________________________________________ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure >
_______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
