El vie, 10-11-2017 a las 09:12 -0500, Neal Gompa escribió: > On Fri, Nov 10, 2017 at 9:04 AM, Zbigniew Jędrzejewski-Szmek > <zbyszek@xxxxxxxxx> wrote: > > On Fri, Nov 10, 2017 at 02:45:26PM +0100, Kevin Kofler wrote: > > > Zbigniew Jędrzejewski-Szmek wrote: > > > > The fedora-release package contains stuff that is tied to each > > > > Fedora > > > > version and changes slowly, and it also contains the preset > > > > files for > > > > systemd units, which change fairly often (a few requests per > > > > month). > > > > > > Why not have a separate fedora-presets then? Just like fedora- > > > repos was > > > split out from fedora-release several releases ago. > > > > Well, pfff, no particular reason, at least from my side. Just > > opening > > a new package and going through the (trivial) review, etc., is a > > bit > > of up-front effort, and then releasing updates for two packages is > > always a bit more effort then for one. So instead, I'd want a good > > reason > > to make another package and how that is going to solve something. > > So far I > > haven't seen anything except some hypothetical issues. > > This would allow us to deduplicate the presets shipped in > generic-release and fedora-release, wouldn't it? We do not keep them in sync between fedora-release and generic-release this is because generic-release is there just to provide an example of how you would setup a -release package for a custom forked OS. it is not intended to be a complete drop in for fedora-release. Dennis > And as long has it has a "system-presets" Provides, downstream folks > can swap them easily enough. > > > > -- > 真実はいつも一つ！/ Always, there's only one truth! > _______________________________________________ > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
