> I would stick to mago just to have a short name. I think there are many
> projects whose name mean multiple things and that's not a problem.
>
I think libmago is short enough and it would be better for packaging in the future. If we create a package in the future, mago could be the source package providing as binaries: mago and libmago (and maybe magotests)
> I would stick to mago just to have a short name. I think there are many
> projects whose name mean multiple things and that's not a problem.
>
I think libmago is short enough and it would be better for packaging in the future. If we create a package in the future, mago could be the source package providing as binaries: mago and libmago (and maybe magotests)