Re: Deciding on Fedora Go (Golang) packaging future

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 






----- Original Message -----
> From: "Nicolas Mailhot" <nicolas.mailhot@xxxxxxxxxxx>
> To: "Development discussions related to Fedora" <devel@xxxxxxxxxxxxxxxxxxxxxxx>, golang@xxxxxxxxxxxxxxxxxxxxxxx
> Sent: Monday, March 18, 2019 8:58:39 PM
> Subject: Re: Deciding on Fedora Go (Golang) packaging future
> 
> Le lundi 18 mars 2019 à 04:55 -0400, Jakub Cajka a écrit :
> 
> Hi,
> 
> >  Golist exist based
> > on Nicolas's initial requests and requirements(created based on them
> > by jchaloupka in his free time over one year ago),
> 
> This is quite a simplistic way to present things, which is injust to
> Jan and to me.
> 
> I wished to make Go packaging in Fedora less a manual shore. I wrote
> some shell and lua code to do it. You (and Jan) objected to this code
> and asked me to restructure it around golist. Jan had already written
> most of golist to analyse the Go code he dealt with (not just in an rpm
> context).
> 
> golist is very much Jan's project and design. We collaborated: Jan
> adapted his code so I could plug it within my rpm automation, just like
> I adapted my code around the golist design.
> 
> Some things were indeed added to golist at my request. But, there are
> lots of things in golist I never asked for: some I didn't think of,
> some I had no need of, some I disagreed with, some that made my life a
> lot harder than it should have been rpm macro-side.
> 
> And, Jan could probably say the same things about my rpm shell+lua
> macro code.
> 
> So, to give everyone's his due, the Fedora rpm macro code is my work
> and design, with some collaboration by Jan, and the golist code is
> Jan's work and design, with some collaboration by me.
> 
> We definitely didn't always agree or approve the design decisions the
> other made. We made do with those disagreements, which is how things
> can move forward in a team.
> 
> Best regards,
> 
> --
> Nicolas Mailhot

Yes this is what I have been trying to convey, sorry that is wasn't obvious(although I have consciously omitted that something similar is part of Gofed as it is IMHO not relevant in this context). As you wrote golist that is part of the Fedora is there based on your request and requirements. If you have not requested it, it wouldn't been there/here.

JC

> _______________________________________________
> devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
> 
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux