Re: Translating Go modules buildrequires in rpm syntax

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

 






----- Original Message -----
> From: "Nicolas Mailhot" <nicolas.mailhot@xxxxxxxxxxx>
> To: "Discussion of RPM packaging standards and practices for Fedora" <packaging@xxxxxxxxxxxxxxxxxxxxxxx>
> Cc: golang@xxxxxxxxxxxxxxxxxxxxxxx, "Jakub Cajka" <jcajka@xxxxxxxxxx>
> Sent: Tuesday, April 2, 2019 1:27:09 PM
> Subject: Re: [Fedora-packaging] Re: Translating Go modules buildrequires in rpm syntax
> 
> Le 2019-04-02 12:52, Jakub Cajka a écrit :
> 
> > I might have not been clear, sorry. My point is more that we don't
> > need to recreate/capture the constrains in the spec files/RPM as they
> > are already capture in the Go source code,
> 
> In the Go module world the constrains are in the module files, not in
> the source files. If you don't satisfy the constrains in your build root
> lots of go commands will break. So you better tell the rpm tooling what
> the constrains are so build roots are populated correctly.
> 

And they are part of the checked in source tree of the respective Go project, if I'm not mistaken.

> > creating part that needs to be (manually) maintained up to date,
> 
> There's nothing to maintain manually if you integrate properly with rpm.
> That's why spec generators like gofed, that try to avoid the rpm
> integration part, do not pass the maintainability test.
> 
> Integrating properly means
> https://github.com/rpm-software-management/rpm/issues/104


Which is not yet there, right?

> 
> > while the GC tooling will enforce them anyway.
> 
> ie builds will fail because the build environment is not populated
> correctly. It'd rather populate it automatically and correctly by
> default than wait for builds to fail and then spend time on manual
> workarounds because the tooling does not help me.
> 

Great to hear that you are working on the packaging automation.

JC

> --
> Nicolas Mailhot
> 
_______________________________________________
packaging mailing list -- packaging@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to packaging-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/packaging@xxxxxxxxxxxxxxxxxxxxxxx




[Index of Archives]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Forum]     [KDE Users]

  Powered by Linux