Re: Packaging for cbind/cview
Hi Michael,
On Sun, Mar 28, 2021 at 11:33:33PM -0700, Micheal Waltz wrote:
> Nilesh,
>
> Wanted to split a thread off of the other packaging thread for Amfora
> since cbind/cview seems to have some additional complications around it.
Sure.
> In the cbind release, 0.1.5, it also has a notice that it's moving to a
> new gitea repo: https://code.rocketnine.space/tslocum/cbind
Wow, this is just plain annoying :-P
And they did it quite literally *yesterday* (11 hours earlier from my
time writing this mail)
> I believe the gitlab repo should still be packaged for go, since there
> are probably some things (including Amfora) that will reference the
> gitlab godep location and not the new gitea one
> This also causes an issues when building 0.1.5 from the gitlab repo,
> and gives an error about missing a package from the new gitea repo and
> therefore I believe only 0.1.4 will build from gitlab,
You can simply change the XS-Go-Import-Path in d/control and it should
work for the error you pasted.
> For now 0.1.4-1 is packaged, uploaded to mentors, and pushed to salsa
> if you could review,
cbind uploaded! Thanks for your work on this :-)
> For the new gitea repo, I'm assuming this is a whole new ITP, RFS and
> package workflow since the package name will be different.
It depends. We can use the same gitlab name if you want, but yes this
brings in a lot of confusion. I've observed that golang libraries are
accepted pretty soon by the FTP masters, so maybe this is not a problem.
However, removing the gitab 0.14 one might be a mess.
>I'll work on putting those in, but for now will focus on the original gitlab
> packages.
Yeah, sure. IMHO, could you please talk with upstream please? They could
atleast *mirror* the development that they do on code.rocketnine.space
on gitlab?
That way, we save a lot of work and the golang libraries that
depends on it can simply use the gitlab library import as well.
Moving around things only adds to inconvinience for everyone.
> I also assume that cview will also under a similar change of
> repo locations since it's developed by the same upstream author.
Yep, sure.
PS: Please consider to simply "Reply to list" i.e. do not reply to me
and CC to the list - or do not click on "Reply all". If you do the latter, I get two mails and it causes
clutter in my mailbox. I read all mails on the list, so there is no need
to mail me explicitly along with the list.
Nilesh
Reply to: