Hello all,
as i have done preliminary work on packaging letsencrypt tool called
acmetool, i would like to ask what would be best course of action to
push packages to devel:language:go and after that into
factory as is.
Everything boils down to one question:
Should i vendor in everything so i can "just" build binary or
repackage binary (was doing that too for my own purpose until i built
all dependencies by hand :) )?
acmetool: https://github.com/hlandau/acme
from source acmetool:
https://build.opensuse.org/project/show/home:bmanojlovic:golang
binary package acmetool:
https://build.opensuse.org/package/show/home:bmanojlovic:webmail/acmetool
Boris
P.S. packages are roughly built for this to work, so it will take time
to SR then into devel:language:go
--
To unsubscribe, e-mail: opensuse-go+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-go+owner(a)opensuse.org
> found conflict of go-tools-1.9+git20170824.5d2fd3cc-11.3.x86_64 with
> ruby2.5-rubygem-bundler-1.16.0-1.2.x86_64:
> - /usr/bin/bundle
That's happening because now the go-tools package ships a new binary
named bundle: https://godoc.org/golang.org/x/tools/cmd/bundle
We could rename this cli too to be /usr/bin/go-bundle for example, but
that would be confusing for go developers installing the package.
How do you think we should solve the issue?
Cheers
Flavio
--
To unsubscribe, e-mail: opensuse-go+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-go+owner(a)opensuse.org
Hi go experts,
could someone please have a look at the following request? It is
already 6 month old...
https://build.opensuse.org/request/show/512349
In case there are errors or packaging faults, please speak up, I would
be glad to fix those.
Thanks in advance,
Johannes
