Re: preparing a 2.14 release

Hi Kili,

thanks for the detailed explanation!

I was indeed afraid that the dependency on graphviz could be a hassle,
so it seems that after all it is not that much of a problem.

Guillaume


2017-12-20 18:52 GMT-03:00 Matthias Kilian <[email protected]>:
> [little bit offtopic]
>
> Hi,
>
> tl;dr: don't let weird OpenBSD patches only appearing in the OpenBSD
> ports tree disturb yout release process.
>
> On Wed, Dec 20, 2017 at 12:50:32PM -0300, Guillaume Hoffmann wrote:
>> Also, the OpenBSD maintainers have re-enabled `show dependencies` [1]
>> so it does not seem that it is a blocker anymore.
>
> I only noticed now that you considered adding a flag for disabling
> show dependencies. Many thanks for that (and keeping an eye on what
> projects like OpenBSD are doing) ;-)
>
> So let me explain *why* I initially patched it away from the OpenBSD
> port:
>
> In OpenBSD, it's possible for a maintainer to update his existing
> ports, even without any ok from other developers, but adding *new*
> ports (graphviz and further dependencies in this case) *needs* an
> explcit ok from other developers.
>
> While I was in 'ghc update mode' back in november, which isa lot
> of really boring work in OpenBSD ports (updating all of our hs-ports),
> I just wanted to get the update of our darcs port (and everything
> else I had in my ports tree) committed ASAP. So I decided to disable
> show dependencies and re-enable it later (which I actually did,
> after I got the oks for graphviz and its additional dependencies).
>
> In any case: whenever you (darcs upstream) are planning a new release
> of darcs, *please* don't hold it back just because there appears
> to be a problem with our OpenBSD port.
>
> Even if there's a real issue (which wasn't the case with show
> dependencies), I could always add a patch local ports tree and then,
> if the patch seems to be useful for everyone else, submit it to you
> to give it a chance to appear in the *next* darcs release.
>
> Ciao,
>         Kili