https://bugzilla.redhat.com/show_bug.cgi?id=2154514 --- Comment #16 from Mike Rochefort <mroche@xxxxxxxxxx> --- > This is not enough, Hare programs including the time::chrono module, even indirectly, need this file to be installed at run time. As you said, that's something that can be handled by a dependency generator macro. For full transparency, right now I'm focusing on end-users being able to *use* Hare in Fedora, not maintainers packaging Hare authored software. If there needs to be a realignment on that, that's fine. I'm just focusing on what's absolutely needed for developers to start using the tool, and then performing incremental enhancements to round everything out. > How do you do that? The makefile that produces /usr/bin/hare with its default configuration for cross compilation, so from the sound of it you'd have to ship 3 hare binaries: one for the regular package and one for each cross toolchain. I think we're talking past each other here a bit. The gnu/llvm split I mentioned would be contingent on Hare being able to accept build-time overrides for those tools. In looking through the Hare source, it doesn't seem like that's the case today, but it's a discussion I can start on the hare-dev list. And adding -gnu even if it's the only sub-package available just implies it's for the gcc/binutils cross-compile toolset considering Clang/LLVM don't require separate tooling to my knowledge. [As a side note, both Alpine and your spec include a definition for arch-ar. I didn't see this referenced anywhere in the Hare source. I do see harec as giving the option of which archive tool to use for compiling its code, but that's it.] > As an end user this sounds like the opposite of the complications I'd want on day 1. This just goes back to my earlier statement, I'm viewing things with two different end-users in mind: developers and package builders/maintainers. I have a number of things I'm thinking about from a macro standpoint, such as build and runtime dependency generators, a provides generator (for modules), and base variables. Right now I'm focusing on making it possible for a Fedora user to install and develop with Hare (hence my COPR). I can continue to build things up that way if it's preferred and make sure the rpm/srpm macros are available as well before acceptance into Fedora, but in my opinion it would better to let people at least play with the technology and get involved in the language's ecosystem first. -- You are receiving this mail because: You are always notified about changes to this product and component You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2154514 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202154514%23c16 -- _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/package-review@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
