Le mercredi 27 mars 2019 à 19:13 +, David Dykstra a écrit :
Hi David,
>
> I'd like to see clarity on the guidelines for golang applications as
> opposed to golang libraries. It seems to assume from the start that
> it's talking about libraries, based on the package naming
> requirement.
From
Robert,
I'd like to see clarity on the guidelines for golang applications as
opposed to golang libraries. It seems to assume from the start that
it's talking about libraries, based on the package naming requirement.
In the "Bundled or de-bundled" section I see mention of "golang projects"
and I s
>
> Sent: Friday, March 22, 2019 7:46:23 PM
> Subject: New Golang Packaging Guidelines: Feedback needed and appreciated
>
> Hello Fedora people,
>
> As you may or may not know, currently applied Golang packaging guidelines
> have always been simply a « draft ». Part of
On Friday, 22 March 2019 22:37:06 CET Fabio Valentini wrote:
>
> Hi Robert-André,
>
> It looks like you put a lot of work into this - I don't think I've
> seen as comprehensive a documentation as this Draft is for any other
> aspect of packaging (but well, Go packaging is notoriously difficult
>
On Fri, Mar 22, 2019 at 7:47 PM Robert-André Mauchin wrote:
>
> Hello Fedora people,
>
> As you may or may not know, currently applied Golang packaging guidelines
> have always been simply a « draft ». Part of the new Go SIG mission is to
> update ours best practices and tooling. As such, Nico
Hello Fedora people,
As you may or may not know, currently applied Golang packaging guidelines
have always been simply a « draft ». Part of the new Go SIG mission is to
update ours best practices and tooling. As such, Nicolas Mailhot designed a
new set of macros based on lua script to impr
