Re: packaging bootstrap example, ideally with golang

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

 



On Sun, May 19, 2019 at 2:23 PM Robert-André Mauchin <zebob.m@xxxxxxxxx> wrote:
>
> Hello,
>
> golang(github.com/jacobsa/ogletest) is only needed for tests by oglemock. So
> you just need to bootstrap oglemock with tests disabled then build ogletest
> then rebuild oglemock unboostrapped.

Thank you for the quick reply!

This makes sense, and I had a feeling this would be the case.

I appreciate the spec files you sent in your second email.

I am not seeing a document that explains how I submit the entire app
for build/update.

I know I can do `fedpkg build` in the various repos, but how do I get
them to all see each other?  in other words, I need oglemock to be
built without tests, build ogletest, then rebuild oglemock and then
build the other dependencies then build the actual app and have this
happen when they all have access to the various dependent files.  I
have not had to package something this complex before.

I don't see a section in the Packaging guide that addresses the
command sequence for this.  Perhaps it is buried in the wiki on a page
that isn't obvious to me?

Can you point me at a document?

I am assuming I can just submit the package and all dependencies in
teh same BZ for review so I am more thinking about the build stage.

thanks,

bx


>
> In the new macros we will have easier tools to deal with more complex cyclic
> dependencies, see my guide: https://eclipseo.fedorapeople.org/guidelines/
> packaging-guidelines/Golang_advanced/#_dealing_with_cyclic_dependencies
>
> _______________________________________________
> 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



-- 
Brian "bex" Exelbierd (he/him/his)
Fedora Community Action & Impact Coordinator
@bexelbie | http://www.winglemeyer.org
bexelbie@xxxxxxxxxx | bex@xxxxxxxxx
_______________________________________________
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