Hi,
which should we choice?
1. use original code and simply change binary/package name "wmdocker",
keep the name in the code uses "docker".
2. use fork on github, everything change to "wmdocker".
Debian/Ubuntu package uses first idea.
On Sun, 24 Apr 2022 20:48:53 +0900,
Stuart Henderson wrote:
>
> On 2022/04/24 11:57, Antoine Jacoutot wrote:
> > On Sun, Apr 24, 2022 at 05:16:13AM +0900, SASANO Takayoshi wrote:
> > > Hi,
> > >
> > > > This conflict with sysutils/docker-cli
> > >
> > > well, should I rework with GitHub's fork https://github.com/mdomlop/wmdocker ?
> > > almost all codes are same as original docker, but version (1.5 -> 1.5.1),
> > > Makefile and application name (docker -> wmdocker) is different.
> >
> > If the fork is more maintained than the original, that would make sense yes :-)
>
> They're equally maintained i.e. not touched since 2003 apart from the
> rename in the fork.
>
> While I would find it amusing for "pkg_add docker" to work it is
> probably best if we don't do that, and use the wmdocker name for the
> binaries/package/port dir.
>
--
SASANO Takayoshi (JG1UAA) <uaa@mx5.nisiq.net>
No comments:
Post a Comment