Support source generation #48
Labels
Comments
|
The FAHC rdgo has been failing due to this. |
cgwalters
added a commit
that referenced
this issue
Aug 9, 2018
Related: #48 This is an easy hack; I'm broadly speaking OK with relying on crates.io for rpm-ostree's CI builds for now. If we take over and replace the Koji stack, we can look at fixing the above issue.
ashcrow
pushed a commit
that referenced
this issue
Aug 9, 2018
Related: #48 This is an easy hack; I'm broadly speaking OK with relying on crates.io for rpm-ostree's CI builds for now. If we take over and replace the Koji stack, we can look at fixing the above issue.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We recently merged Rust code into rpm-ostree. Previously, rpm-ostree was buildable with rdgo. It isn't with
--enable-rustbecause cargo wants to fetch bits from the internets.COPR today has a "Custom" AKA
make srpmpath which generates sources. I think we should do something similar although I'd say we provide a git repository by default, and the process should make one or more commits on top of that. We could also equivalently have the code generate a tarball, and then unpack+commit that, but I like encouraging git.Concretely for rpm-ostree today though we'd probably use the cargo vendor bits which are part of our
automake-based tarball generation.The text was updated successfully, but these errors were encountered: