Hi,
> according to git activity and comments in the issues, adminer seems dead
> upstream.
>
> Part of the community have forked it into adminerevo:
>
> https://docs.adminerevo.org/
>
> Would you consider packaging that instead of adminer ?
Yes, I'm thinking about it and I'm wondering on the strategy regarding
upgrades.
Options are:
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
Maybe Chris can advise here.
Thanks,
Alex
