Thanks to everyone for the comments and review. I have written things
up on the wiki:
https://wiki.debian.org/BuildProfile/upstream-cargo
and added the entry here:
https://wiki.debian.org/BuildProfileSpec
Please comment here, if you think any of this doesn't make sense.
Thanks,
Ian.
--
On Fri, 16 Dec 2022 at 11:01:58 +, Ian Jackson wrote:
> With nopython, we want to *avoid doing the Python things at all*. But
> "the Python things" here isn't "all Python things" - it's "certain
> Python things that appear in the outputs". So that can't be done as a
> blanket exclusion on
Quoting Russ Allbery (2022-12-16 17:07:00)
> Jonas Smedegaard writes:
> > Quoting Russ Allbery (2022-12-15 17:41:15)
>
> >> This is why I don't agree with Jonas: yes, there *are* other ways to
> >> achieve the same goal, but they're more complicated and harder to
> >> explain. The user
Jonas Smedegaard writes:
> Quoting Russ Allbery (2022-12-15 17:41:15)
>> This is why I don't agree with Jonas: yes, there *are* other ways to
>> achieve the same goal, but they're more complicated and harder to
>> explain. The user experience of this build profile looks a lot simpler
>> and
Quoting Russ Allbery (2022-12-15 17:41:15)
> Ian Jackson writes:
>
> > I would like to add the following entry to the table of build
> > profiles in BuildProfileSpec:
>
> > Profile anme: `cargo-upstream`
> > Can cause changes to built binaries, including functional chnges. (Y)
> > Should not
Helmut Grohne writes ("Re: Proposed `cargo-upstream` dpkg-buildpackage etc.
build profile"):
> On Thu, Dec 15, 2022 at 11:44:34PM +, Ian Jackson wrote:
> > I'm not sure precisely how this feature could (or should) be made
> > available to *all* application packages
Hi Ian,
On Thu, Dec 15, 2022 at 11:44:34PM +, Ian Jackson wrote:
> I'm not sure precisely how this feature could (or should) be made
> available to *all* application packages in a central way. Having
> tools like debcargo automatically add the profile to the build deps
> produces a lot of
Helmut Grohne writes ("Re: Proposed `cargo-upstream` dpkg-buildpackage etc.
build profile"):
> Thank you very much for immediately taking this to the list.
You're welcome.
Thanks for the review and the penetrating questions.
> I think that you imply here that all of the rust
Hi Ian,
Thank you very much for immediately taking this to the list. The
discussion I've seen thus far seems very constructive and useful to me.
Thanks to the other participants as well.
On Thu, Dec 15, 2022 at 10:41:13AM +, Ian Jackson wrote:
> I would like to add the following entry to the
Ian Jackson writes:
> I would like to add the following entry to the table of build
> profiles in BuildProfileSpec:
> Profile anme: `cargo-upstream`
> Can cause changes to built binaries, including functional chnges. (Y)
> Should not cause changes to set of build debs. (N)
> Description:
>
Quoting Ian Jackson (2022-12-15 14:05:32)
> Jonas Smedegaard writes ("Re: Proposed `cargo-upstream` dpkg-buildpackage
> etc. build profile"):
> > What is the benefit of introducing a standardized flag for this
> > relatively narrow scope, compared to doing non-standar
Wouter Verhelst writes ("Re: Proposed `cargo-upstream` dpkg-buildpackage etc.
build profile"):
> I have just one question: why make this rust-specific? I think a similar
> thing might be useful for golang packages (who also don't support shared
> libraries), or, heck, even P
Jonas Smedegaard writes ("Re: Proposed `cargo-upstream` dpkg-buildpackage etc.
build profile"):
> Similar pain for other upstream ecosystems as well - I know about npm
> for NodeJS modules, but imagine it is similar for Java and others as
> well.
Yes.
> What is the
Hi Ian,
On Thu, Dec 15, 2022 at 10:41:13AM +, Ian Jackson wrote:
> I would like to add the following entry to the table of build
> profiles in BuildProfileSpec:
>
> Profile anme: `cargo-upstream`
> Can cause changes to built binaries, including functional chnges. (Y)
> Should not cause
[ reply to d-devel only, as more suitable for Debian-wide issue ]
Quoting Ian Jackson (2022-12-15 11:41:13)
> I would like to add the following entry to the table of build
> profiles in BuildProfileSpec:
>
> Profile anme: `cargo-upstream`
> Can cause changes to built binaries, including
I would like to add the following entry to the table of build
profiles in BuildProfileSpec:
Profile anme: `cargo-upstream`
Can cause changes to built binaries, including functional chnges. (Y)
Should not cause changes to set of build debs. (N)
Description:
Obtain Rust dependencies from
16 matches
Mail list logo
