Hi Alexandre,
> 1) new package src:adminerevo providing adminer and removal of src:adminer
>
> Advantages : explicit branding
>
> 2) src:adminer using adminerevo source and building adminer pkg
>
> Advantages : easy upgrade path (no Provides:, Conflicts:, no conffile
> moving around in postinst)
>
> 3) src:adminer using adminerevo source and building adminerevo pkg
>
> Advantages : explicit branding for binary package and easier
> going back if src:adminer ever comes back alive
Hmm. Unfortunately I'm a little bit out of the loop with adminer
stuff so I won't be able to provide anything close to reliable
guidance.
However, I'm a little hesitant re. using the existing src:adminer with
the adminerevo source (ie. #2 and #3) on philosophical/aesthetic
grounds. It just feels "right" to have a different source package for
that.
Perhaps consider raising this on debian-devel for clarification,
otherwise I'd go with #1.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org 🍥 chris-lamb.co.uk
`-
