Sunday, January 31, 2021

Re: replace security/stegcracker with security/stegseek

Hi,

Am Freitag, Januar 29, 2021 19:22 CET, schrieb Klemens Nanni <kn@openbsd.org>:

> On Thu, Jan 28, 2021 at 11:28:10PM +0100, Sebastian Reitenbach wrote:
> > for the quirks, just use reason 3: "no longer maintained upstream"
> > or add a new one: "no longer maintained upstream, suggest stegseek" ?
> Just add new ones if need be, no need to be less specific.
>

Will do thanks,

> But if one replaces the other, why not merge the old into the new one
> and keep users on track?

you mean to place the stegseek port into the stegcracker directory?
Or is there an easy way with @conflict etc. markers in PLIST ?


cheers,
Sebastian

No comments:

Post a Comment