----- Original Message ----- > From: "Athos Ribeiro" <athoscribeiro@xxxxxxxxx> > To: "Development discussions related to Fedora" <devel@xxxxxxxxxxxxxxxxxxxxxxx> > Sent: Thursday, August 2, 2018 11:14:51 PM > Subject: Re: Golang SIG for Fedora > > On Thu, Aug 02, 2018 at 02:45:54PM -0500, Michael Cronenworth wrote: > > On 07/27/2018 08:28 AM, Jakub Cajka wrote: > > > There are few big outstanding issues that needs to be solved that need > > > more than individual work, most notably the Go packaging guidelines > > > and tooling. I think that should be one of the first tasks for the > > > SIG. > > > > I'm not looking to join the SIG, but I will share my experience with golang > > in Fedora. > > > > It appears that packages are being dumped into Fedora and forgotten about. > > I'm trying to package "Packer"[1] and ran into multiple dependencies that > > were committed once and never updated. This has to change. > > In my experience, the tough parts about these dependencies that got > forgot about are: > > 1) they are only dependencies, nobody uses them for anything else; Afaik this only reason that we have so many golang-* package they are "only de-bundled dependencies" for other golang base packages they are not meant to be used as devel packages(for developing application for Fedora). One solution to this would be going back to the bundling which is IMHO much worse. For the record not all packages are debundled, though. Maybe other solution might be if we will be able to drive more people to do the Go packaging, because I don't believe that packagers with 100s of packages will baby sit each of them, they will thereat them more as cattle only looking at then when it is really necessary. Maybe the best solution would be to continue with work that jchaloup has started making the Go packaging in Fedora mostly automated. > 2) many of them are not versioned upstream (we just have references to > commits) Afaik also commonly not maintaining API stability... > 3) different applications that depend on them may need different > revisions of them. > > while solving 3 is part of our duty as packagers (making sure to port the > dependencies to use the latest versions of their dependencies), 2 seems > to be quite common in the golang community... Hopefully with upstream work on vgo and other dependency managers will be improvement for this. JC > > -- > Athos Ribeiro > > http://www.ime.usp.br/~athoscr > _______________________________________________ > 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/message/AID5NXKVSVTU55E4GRUK6LE2XZRL5YPL/ > _______________________________________________ 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/message/ARWI62INSJCGN4LIAI7IR6LL3IV3IMQ3/
