<p dir="ltr">On Sep 10, 2015 10:27 AM, "Paul W. Frields" <<a href="mailto:stickster@gmail.com">stickster@gmail.com</a>> wrote:<br>
><br>
> On Thu, Sep 10, 2015 at 09:45:50AM -0400, Máirín Duffy wrote:<br>
> > Okay, so from what I understand thus far then:<br>
> ><br>
> > 1) If I upgrade to F23, I will either be left with F22 darktable and get<br>
> > confused/frustrated when I try to upgrade it (eg when a new feature comes<br>
> > out tha tI want,) or I will be left with a system that I cannot upgrade at<br>
> > all (still an open question as to how obvious the workaround of removing<br>
> > darktable would be?)<br>
> ><br>
> > 2) The Design Suite is going to either (a) drop darktable (b) be dropped<br>
> > itself (c) massively overhauled to become a Fedora Remix.<br>
> ><br>
> > 3) Still don't understand the F23 experience of installing darktable.<br>
> ><br>
> > In terms of user experience, this simply sucks and makes me feel like<br>
> > slavish adherence to obscure packaging rules is more important than our user<br>
> > base.<br>
><br>
> /me catches up with thread<br>
><br>
> I'm not sure if 2(c) is necessary, if we have disabled repo support,<br>
> but I don't understand how that works with the upgrade process. Need<br>
> moar clue?<br>
></p>
<p dir="ltr">I don't know the full details of the disabled repo support, but is there a way to add a script that checks whether the user has darktable currently installed and if so then automatically enable the repo? This way the first upgrade will have the previously mainline package swapped with the copr package?</p>
<p dir="ltr">> But agreed, this is truly disappointing and doesn't appear that Fedora<br>
> is acting like "friends" in the case of a well-maintained and tightly<br>
> integrated upstream. A slavish, single-minded approach to all<br>
> upstreams is going to basically force the state (brought up earlier in<br>
> the thread) where meaningful future apps all go to COPR.</p>
<p dir="ltr">I agree, the people who made the decision to kick darktable need to say "We screwed up" and immediately bring it back in. This kind of policy will guarantee that future packagers to Fedora will either just do it through Copr, or just do it via an external repo.</p>