Re: Rust-team branch status?

On Thu, Jun 27, 2024 at 03:09:16PM +0200, Tomas Volf wrote: > Hello, > > On 2024-06-27 05:50:02 -0700, Felix Lechner via Development of GNU Guix and > the GNU System distribution. wrote: > > Hi Efraim, > > > > On Wed, Jun 26 2024, Efraim Flashner wrote: > > > > > The packages are public but hidde

Re: Rust-team branch status?

Hello, On 2024-06-27 05:50:02 -0700, Felix Lechner via Development of GNU Guix and the GNU System distribution. wrote: > Hi Efraim, > > On Wed, Jun 26 2024, Efraim Flashner wrote: > > > The packages are public but hidden > > Interesting! How does that work, please? I looked at the package > def

Re: Rust-team branch status?

Hi Efraim, On Wed, Jun 26 2024, Efraim Flashner wrote: > The packages are public but hidden Interesting! How does that work, please? I looked at the package definition [1] but could not see fields that hide it. Thanks! Kind regards Felix [1] https://git.savannah.gnu.org/cgit/guix.git/tree/g

Re: Rust-team branch status?

Efraim Flashner writes: [[PGP Signed Part:Undecided]] On Wed, Jun 26, 2024 at 10:46:56AM +0300, Efraim Flashner wrote: On Tue, Jun 25, 2024 at 08:48:12AM -0700, Ian Eure wrote: > Hi Efraim, > > Efraim Flashner writes: > > > [[PGP Signed Part:Undecided]] > > On Thu, Jun 20, 2024 at 05:10:

Re: Rust-team branch status?

On Wed, Jun 26, 2024 at 10:46:56AM +0300, Efraim Flashner wrote: > On Tue, Jun 25, 2024 at 08:48:12AM -0700, Ian Eure wrote: > > Hi Efraim, > > > > Efraim Flashner writes: > > > > > [[PGP Signed Part:Undecided]] > > > On Thu, Jun 20, 2024 at 05:10:11PM -0700, Ian Eure wrote: > > > > Hi Guixers,

Re: Rust-team branch status?

On Tue, Jun 25, 2024 at 08:48:12AM -0700, Ian Eure wrote: > Hi Efraim, > > Efraim Flashner writes: > > > [[PGP Signed Part:Undecided]] > > On Thu, Jun 20, 2024 at 05:10:11PM -0700, Ian Eure wrote: > > > Hi Guixers, > > > > > > I want to update the Librewolf package, but it now depends on Rust >

Re: Rust-team branch status?

Hi Efraim, Efraim Flashner writes: [[PGP Signed Part:Undecided]] On Thu, Jun 20, 2024 at 05:10:11PM -0700, Ian Eure wrote: Hi Guixers, I want to update the Librewolf package, but it now depends on Rust >= 1.76, which is newer than what's in master. I see the >rust-team branch has versions

Re: Rust-team branch status?

Hi Efraim, On Fri, Jun 21 2024, Efraim Flashner wrote: > I managed to burn myself out on rust stuff a few months ago Thank you for your hard work. Rust is perhaps the most complex part in the Guix packaging effort. > After merging the current branch I hope to be able to move the version > of r

Re: Rust-team branch status?

On Thu, Jun 20, 2024 at 05:10:11PM -0700, Ian Eure wrote: > Hi Guixers, > > I want to update the Librewolf package, but it now depends on Rust >= 1.76, > which is newer than what's in master. I see the rust-team branch has > versions up to 1.77 — is there a timeline for merging that, or a TODO

Re: rust-team branch merged

Efraim Flashner writes: [[PGP Signed Part:Undecided]] On Wed, Apr 24, 2024 at 11:58:22AM -0400, Jason Conroy wrote: Efraim Flashner writes: > On the other hand, by generating it during the build of each > package we > make sure to pull in all the crates which exist in the build, > so we

Re: rust-team branch merged

On Wed, Apr 24, 2024 at 11:58:22AM -0400, Jason Conroy wrote: > > Efraim Flashner writes: > > On the other hand, by generating it during the build of each package we > > make sure to pull in all the crates which exist in the build, so we > > could add into a profile/manifest just the crates liste

Re: rust-team branch merged

Efraim Flashner writes: On the other hand, by generating it during the build of each package we make sure to pull in all the crates which exist in the build, so we could add into a profile/manifest just the crates listed in a Cargo.toml and then each crate would pull in its own dependencies,

Re: rust-team branch merged

On Thu, Apr 18, 2024 at 12:54:02PM -0400, Jason Conroy wrote: > > Efraim Flashner writes: > > > Currently if you were to pull in rust-rand-0.8 and rust-rand-0.7 then > > you'd have both rand-0.*.crate files in the registry but only one of > > them would be listed in share/cargo/registry/index/ra

Re: rust-team branch merged

Efraim Flashner writes: Currently if you were to pull in rust-rand-0.8 and rust-rand-0.7 then you'd have both rand-0.*.crate files in the registry but only one of them would be listed in share/cargo/registry/index/ra/nd/rand. I need to adjust the generation of that file to combine multiple

Re: rust-team branch merged

On Tue, Mar 12, 2024 at 11:12 AM Efraim Flashner wrote: > On Thu, Mar 07, 2024 at 11:48:53AM -0500, Jason Conroy wrote: > > On Thu, Mar 7, 2024 at 3:08 AM Efraim Flashner > > wrote: > > > > > Until then > > > I've been experimenting by manually listing the other crates I've > needed > > > but in

Re: rust-team branch merged

On Thu, Mar 7, 2024 at 3:08 AM Efraim Flashner wrote: > The transitive dependencies getting pulled in automatically should work > automatically if we ever finish the antioxidant-build-system. Since you bring up antioxidant, I'm kind of curious whether that stalled mainly due to shifts in contri

Re: rust-team branch merged

On Wed, Mar 6, 2024 at 4:06 AM Efraim Flashner wrote: > On Mon, Feb 26, 2024 at 09:24:29PM -0500, Jason Conroy wrote: > > Hello Efraim, > > > > Thanks for investigating this - a Rust development workflow using only > > Guix-native crates is something I've been waiting for! > > > > I was experimen

Re: rust-team branch merged

On Thu, Mar 07, 2024 at 11:48:53AM -0500, Jason Conroy wrote: > On Thu, Mar 7, 2024 at 3:08 AM Efraim Flashner > wrote: > > > The transitive dependencies getting pulled in automatically should work > > automatically if we ever finish the antioxidant-build-system. > > > Since you bring up antiox

Re: rust-team branch merged

On Wed, Mar 06, 2024 at 12:53:44PM -0500, Jason Conroy wrote: > On Wed, Mar 6, 2024 at 4:06 AM Efraim Flashner > wrote: > > > On Mon, Feb 26, 2024 at 09:24:29PM -0500, Jason Conroy wrote: > > > Hello Efraim, > > > > > > Thanks for investigating this - a Rust development workflow using only > > >

Re: rust-team branch merged

On Mon, Feb 26, 2024 at 09:24:29PM -0500, Jason Conroy wrote: > Hello Efraim, > > Thanks for investigating this - a Rust development workflow using only > Guix-native crates is something I've been waiting for! > > I was experimenting with your patches and it seems that they do pull in the > sourc

Re: Rust team branch merged

On Thu, Feb 29, 2024, at 02:11, Efraim Flashner wrote: > * Most of the packages in rust-apps have been upgraded. > * rav1e was upgraded from 0.6.6 to 0.7.1 > * dav1d was upgraded from 1.0.0 to 1.3.0 > * libaom was upgraded from 3.5.0 to 3.8.0 Thanks for updating these AV1 video packages!

Re: Rust team branch merged

On Wed, Feb 28, 2024 at 01:53:13PM +0100, Andreas Enge wrote: > $ git status > On branch master > Your branch is behind 'origin/master' by 1438 commits, and can be > fast-forwarded. > (use "git pull" to update your local branch) > > $ git log origin/master > commit f29f80c194d0c534a92354b2bc19

Re: Rust team branch merged

Hi Rust Team, On Wed, Feb 28 2024, Andreas Enge wrote: > Congratulations to the Rust team (aka Efraim) for this big endeavour! How timely are your good news! Please let this article brighten your day. https://www.infoworld.com/article/3713203/white-house-urges-developers-to-dump-c-and-c.html

Re: rust-team branch merged

Hello Efraim, Thanks for investigating this - a Rust development workflow using only Guix-native crates is something I've been waiting for! I was experimenting with your patches and it seems that they do pull in the source crates for requested packages, but not their dependencies (example below).

Re: Rust <3 Guix

On Mon, Dec 25, 2023 at 07:25:26AM +, jgart wrote: > > Do you need both nss-certs and curl? > > Hi Efraim, yes, I need both, oddly enough. If I remove one of them the build > fails with the error message in the README that I provided. > > > I saw in a later commit you said it's working. > >

Re: Rust <3 Guix

> Do you need both nss-certs and curl? Hi Efraim, yes, I need both, oddly enough. If I remove one of them the build fails with the error message in the README that I provided. > I saw in a later commit you said it's working. I'm able to build main.rs with the guix installed tools but I'm not ab

Re: Rust <3 Guix

On Sun, Dec 24, 2023 at 08:35:36PM +, jgart wrote: > Hi Guixers, > > What do you think I am missing? > > Completion works. > Clippy works. > Rustfmt works. > > `rust-compile` from emacs-rust-mode does not work :( > > I get the following error listed in the README when I try to compile the

Re: rust-team branch merged

Efraim Flashner writes: > The rust team is pleased to announce that the rust-team branch has been > merged back into master. There are 570 commits across the branch. > Cross-compiling support for the cargo-build-system was added, including > for librsvg. Cross-compiling was tested for (nearly)

Re: rust-team branch merged

On Wed, Dec 13, 2023 at 10:34:11AM +0200, Efraim Flashner wrote: > * Compiled rust packages currently have a 'package' phase, which runs > the command used to crate a 'crate tarball', and is installed in > %output/share/cargo/registry, with unpacked sources in > %output/share/cargo/src. In theory

Re: rust-team branch merged

Hi Efraim, Efraim Flashner writes: > The rust team is pleased to announce that the rust-team branch has been > merged back into master. There are 570 commits across the branch. > Cross-compiling support for the cargo-build-system was added, including > for librsvg. Cross-compiling was tested f

Re: rust-build-system from antioxidant

Hi Nicolas, Nicolas Graves writes: > Hi all, > > Thanks for this discussion that I didn't expected to happen ;) > > I'll try and finish a version of the rust-build-system but I'd like to > know if there are reasons to not want a direct and complete rewrite of > all Rust packages before putting m

Re: rust-build-system from antioxidant

Hi all, Thanks for this discussion that I didn't expected to happen ;) I'll try and finish a version of the rust-build-system but I'd like to know if there are reasons to not want a direct and complete rewrite of all Rust packages before putting more time into this. My rationale is that since w

Re: rust-build-system from antioxidant

Op 12-06-2023 om 15:05 schreef Maxim Cournoyer: Hi Maxime, Maxime Devos writes: Op 12-06-2023 om 03:17 schreef Maxim Cournoyer: [...] Yes. Overruling is a form of blocking, and blocking by authority (whether de facto or de jure) is overruling. There should not be a notion of 'overruling'

Re: rust-build-system from antioxidant

Hi Vagrant, On Mon, Jun 12, 2023 at 8:09 AM Vagrant Cascadian wrote: > > everything kind of has a social component! Thank you for pointing that out! Many technical discussions about project governance claim high moral ground but remain incomplete. Maxime possibly felt some righteous indignation

Re: rust-build-system from antioxidant

On 2023-06-11, Maxim Cournoyer wrote: > Maxime Devos writes: >> Op 02-06-2023 om 20:02 schreef Nicolas Graves: >>> A few months ago, Maxime Devos worked on a new rust-build-system to >>> handle a few issues we were experiencing with cargo (see discussions on >>> antioxidant in guix-devel). >>> A m

Re: rust-build-system from antioxidant

Hi Maxime, Maxime Devos writes: > Op 12-06-2023 om 03:17 schreef Maxim Cournoyer: >> Hi Maxime, >> Maxime Devos writes: >> >>> Op 02-06-2023 om 20:02 schreef Nicolas Graves: A few months ago, Maxime Devos worked on a new rust-build-system to handle a few issues we were experiencing w

Re: rust-build-system from antioxidant

Op 12-06-2023 om 03:17 schreef Maxim Cournoyer: Hi Maxime, Maxime Devos writes: Op 02-06-2023 om 20:02 schreef Nicolas Graves: A few months ago, Maxime Devos worked on a new rust-build-system to handle a few issues we were experiencing with cargo (see discussions on antioxidant in guix-devel

Re: rust-build-system from antioxidant

Hi Maxime, Maxime Devos writes: > Op 02-06-2023 om 20:02 schreef Nicolas Graves: >> A few months ago, Maxime Devos worked on a new rust-build-system to >> handle a few issues we were experiencing with cargo (see discussions on >> antioxidant in guix-devel). >> A month ago, we discussed about the

Re: rust-build-system from antioxidant

Op 02-06-2023 om 20:02 schreef Nicolas Graves: A few months ago, Maxime Devos worked on a new rust-build-system to handle a few issues we were experiencing with cargo (see discussions on antioxidant in guix-devel). A month ago, we discussed about the possibility of the integration in core guix,

Re: rust-team branch merged

On Tue, May 09, 2023 at 02:22:36PM +0100, Christopher Baines wrote: > > Andreas Enge writes: > > > Hello, > > > > Am Tue, May 09, 2023 at 11:54:00AM +0300 schrieb Efraim Flashner: > >> The way its currently setup all we need to do is re-add aarch64-linux to > >> the supported-systems of rust-boo

Re: rust-team branch merged

Andreas Enge writes: > Hello, > > Am Tue, May 09, 2023 at 11:54:00AM +0300 schrieb Efraim Flashner: >> The way its currently setup all we need to do is re-add aarch64-linux to >> the supported-systems of rust-bootstrap and it'll be enabled again, and >> build successfully eventually. > > I am co

Re: rust-team branch merged

PS: Congratulations for getting the first team branch through! And thanks for waiting until the core-updates merge :-)

Re: rust-team branch merged

Hello, Am Tue, May 09, 2023 at 11:54:00AM +0300 schrieb Efraim Flashner: > The way its currently setup all we need to do is re-add aarch64-linux to > the supported-systems of rust-bootstrap and it'll be enabled again, and > build successfully eventually. I am confused by what happened; did you di

Re: rust-team branch merged

On Tue, May 09, 2023 at 09:33:46AM +0100, Christopher Baines wrote: > > Efraim Flashner writes: > > > I've merged the rust-team branch into master. I've dropped rust for > > aarch64-linux again for now until I can get it built on cuirass so it's > > not holding up the branch any longer. > > Do

Re: rust-team branch merged

Efraim Flashner writes: > I've merged the rust-team branch into master. I've dropped rust for > aarch64-linux again for now until I can get it built on cuirass so it's > not holding up the branch any longer. Do you know if it actually doesn't build, or whether it's just a berlin/Cuirass issue?

Re: [Rust Team] Status post core-updates merge

Hi Efraim, Efraim Flashner writes: [...] >> I'm also curious, since you're "early adopters": how are you managing >> with the team workflow? Any tips, remarks or impressions that you could >> share with other teams? > > Speak in the plural and no one will realize it's a team of one ;) > > I'm

Re: [Rust Team] Status post core-updates merge

On Thu, Apr 27, 2023 at 07:06:29PM +0200, Josselin Poiret wrote: > Hi Efraim (and the rest of the Rust team), > > Efraim Flashner writes: > > > Now that core-updates has been merged into master it's time for a status > > update from the rust team. > > > > Currently rust supports (in the order of

Re: [Rust Team] Status post core-updates merge

Hi Efraim (and the rest of the Rust team), Efraim Flashner writes: > Now that core-updates has been merged into master it's time for a status > update from the rust team. > > Currently rust supports (in the order of gaining support) x86_64, > aarch64 and riscv64. GDB-11 doesn't currently build o

Re: rust-team cuirass build

Efraim Flashner writes: > The Rust Team has been hard at work updating the rust compiler and a > number of rust packages. We've tested a number of packages¹ to ensure > that everything looks okay. > > Quick stats for the branch: > 404 commits by 4 people. > 181 packages updated > 50 packages remo

Re: Rust team branch

Am Tue, Feb 14, 2023 at 10:07:12PM +0200 schrieb Efraim Flashner: > > By "pull out" you mean revert them in staging and apply them on a separate > > branch? That would also delay #61475 and maybe ease merging of the staging > > branch. > I was thinking more of cherry-picking them into a branch, not

Re: Rust team branch (was Re: Discussion notes on releases and branches)

On 2/14/23 1:08 PM, Efraim Flashner wrote: Also I don't think there's a lot of overlap between go and rust so we can probably have both going at the same time. Oh, yes, I didn't mean to imply that the two were related, or conflicted. I just wanted to point it out in case it was of any help.

Re: Rust team branch (was Re: Discussion notes on releases and branches)

On Tue, Feb 14, 2023 at 09:36:46AM -0700, Katherine Cox-Buday wrote: > Efraim Flashner writes: > > > As a project we haven't setup anything for starting the team-based > > branches and upgrades, and the Rust Team volunteers to go first. > > Leo has attempted[1] to setup a branch for Go, but we'r

Re: Rust team branch

On Tue, Feb 14, 2023 at 05:36:13PM +0100, Andreas Enge wrote: > Am Tue, Feb 14, 2023 at 12:14:04PM +0200 schrieb Efraim Flashner: > > On behalf of the Rust Team™¹ we'd like to check our rust source tarballs > > for any hidden binaries² and to do a mass upgrade of many of the crates. > > Currently t

Re: Rust team branch (was Re: Discussion notes on releases and branches)

Efraim Flashner writes: > As a project we haven't setup anything for starting the team-based > branches and upgrades, and the Rust Team volunteers to go first. Leo has attempted[1] to setup a branch for Go, but we're waiting to hear from sysadmins on why there's a build error. [1] https://lists

Re: Rust team branch

Am Tue, Feb 14, 2023 at 12:14:04PM +0200 schrieb Efraim Flashner: > On behalf of the Rust Team™¹ we'd like to check our rust source tarballs > for any hidden binaries² and to do a mass upgrade of many of the crates. > Currently there are many crates queued up in the staging branch but we'd > like t

Re: Rust on aarch64-linux

On Sat, Oct 22, 2022 at 11:22:50PM +0300, Efraim Flashner wrote: > On Fri, Oct 21, 2022 at 10:51:59AM +0200, Ludovic Courtès wrote: > > Hello, > > > > Efraim Flashner skribis: > > > > > I'm not sure there is a bug report, I didn't see it either. It looks > > > like when I bumped rust-bootstrap f

Re: Rust on aarch64-linux

On Fri, Oct 21, 2022 at 10:51:59AM +0200, Ludovic Courtès wrote: > Hello, > > Efraim Flashner skribis: > > > I'm not sure there is a bug report, I didn't see it either. It looks > > like when I bumped rust-bootstrap from 1.39 to 1.54 we lost aarch64 > > support. I've bumped mrustc on staging and

Re: Rust on aarch64-linux

On Fri, Oct 21, 2022 at 10:51:59AM +0200, Ludovic Courtès wrote: > Hello, > > Efraim Flashner skribis: > > > I'm not sure there is a bug report, I didn't see it either. It looks > > like when I bumped rust-bootstrap from 1.39 to 1.54 we lost aarch64 > > support. I've bumped mrustc on staging and

Re: Rust in the kernel

Ludovic Courtès writes: > Hi, > > Akib Azmain Turja skribis: > >>> (During that time, interested readers can also take a stab at improving >>> support for the Hurd, which relies on that revolutionary technology >>> called “address spaces” to ensure Memory Safety™ among other things!) >>> >>> Lud

Re: Rust in the kernel

Hi, Akib Azmain Turja skribis: >> (During that time, interested readers can also take a stab at improving >> support for the Hurd, which relies on that revolutionary technology >> called “address spaces” to ensure Memory Safety™ among other things!) >> >> Ludo’. >> > > Why "address spaces" is a

Re: Rust in the kernel

July 5, 2022 11:36 AM, "Akib Azmain Turja" wrote: > jbra...@dismail.de writes: > >> July 5, 2022 12:48 AM, "Akib Azmain Turja" wrote: >> >>> jbra...@dismail.de writes: >> >> July 4, 2022 1:36 PM, "Akib Azmain Turja" wrote: >> >> Ludovic Courtès writes: >> >> Hi! >> >> Leo Famulari skrib

Re: Rust in the kernel

>BTW, what's the status of Viengoos? The author put it on indefinite hiatus and no one else has the expertise (and/or interest) to continue to work on it.

Re: Rust in the kernel

>GNU Mach, which is what the Hurd runs on. Is slower that Linux. There was an attempt to port the Hurd to L4 before. It is deemed not possible by the current hurd developers. This was done with an older L4 (Pistachio, I think) that lacked capabilities in the kernel. Doing it with SEL4 has not be

Re: Rust in the kernel

jbra...@dismail.de writes: > July 5, 2022 12:48 AM, "Akib Azmain Turja" wrote: > >> jbra...@dismail.de writes: >> >>> July 4, 2022 1:36 PM, "Akib Azmain Turja" wrote: >>> Ludovic Courtès writes: >>> >>> Hi! >>> >>> Leo Famulari skribis: The effort to use the Rust programming lang

Re: Rust in the kernel

July 5, 2022 12:48 AM, "Akib Azmain Turja" wrote: > jbra...@dismail.de writes: > >> July 4, 2022 1:36 PM, "Akib Azmain Turja" wrote: >> >>> Ludovic Courtès writes: >> >> Hi! >> >> Leo Famulari skribis: >>> The effort to use the Rust programming language within the Linux kernel >>> is progr

Re: Rust in the kernel

Ludovic Courtès writes: > Hi! > > Leo Famulari skribis: > >> The effort to use the Rust programming language within the Linux kernel >> is progressing and may be realized in the next few months: >> >> https://lwn.net/SubscriberLink/899182/6c831b90eaee015e/ >> https://www.memorysafety.org/blog/me

Re: Rust in the kernel

jbra...@dismail.de writes: > July 4, 2022 1:36 PM, "Akib Azmain Turja" wrote: > >> Ludovic Courtès writes: >> >>> Hi! >>> >>> Leo Famulari skribis: >> >> The effort to use the Rust programming language within the Linux kernel >> is progressing and may be realized in the next few months: >>

Re: Rust in the kernel

July 4, 2022 1:36 PM, "Akib Azmain Turja" wrote: > Ludovic Courtès writes: > >> Hi! >> >> Leo Famulari skribis: > > The effort to use the Rust programming language within the Linux kernel > is progressing and may be realized in the next few months: > > https://lwn.net/SubscriberLink/899182/

Re: Rust in the kernel

Ludovic Courtès writes: > Hi! > > Leo Famulari skribis: > >> The effort to use the Rust programming language within the Linux kernel >> is progressing and may be realized in the next few months: >> >> https://lwn.net/SubscriberLink/899182/6c831b90eaee015e/ >> https://www.memorysafety.org/blog/me

Re: Rust in the kernel

Hi! Leo Famulari skribis: > The effort to use the Rust programming language within the Linux kernel > is progressing and may be realized in the next few months: > > https://lwn.net/SubscriberLink/899182/6c831b90eaee015e/ > https://www.memorysafety.org/blog/memory-safety-in-linux-kernel/ > > With

Re: Rust in the kernel

On Thu, Jun 30, 2022 at 12:37:54PM -0400, Leo Famulari wrote: > Within Guix, we'll need to adapt our kernel build processes in order to > support this. An update on GCC support for Rust: https://lwn.net/Articles/899385/ signature.asc Description: PGP signature

Re: Rust reprodubility -- .rmeta and shadow-rs

Hello! Maxime Devos skribis: > There was some mail about irreproducibility in Rust, but I couldn't > find it anymore. Anyway, I found a potential cause: rust-shadow-rs > embeds timestamps (even though it nominally respects > SOURCE_DATE_EPOCH???) and the ordering of definitions it generates is

Re: Rust reprodubility -- .rmeta and shadow-rs

> https://issues.guix.gnu.org/50015 I don't think that shadow-rs changes Cargo.toml, so I think that one is a separate issue ... > https://issues.guix.gnu.org/55928 Maybe related, though .rmeta isn't mentioned there so maybe not. Seems debugging information related, so maybe the report at (and f

Re: (rust) Do we always need to package minor versions separately?

Am 08.03.22 um 22:01 schrieb Liliana Marie Prikler: In practice, we assume 0.y.z be compatible with 0.y.a, a < z or the other way round depending on which direction you're looking at. I'm not sure if this is a rust fortification of semver This is backed by the cargo manual

Re: (rust) Do we always need to package minor versions separately?

Hi, Am Dienstag, dem 08.03.2022 um 18:43 +0100 schrieb Maxime Devos: > Hi guix, > > Many rust crates are available in multiple versions in Guix > (say, rust-wayland-scanner-0.29).  The reason is that ((guix)Rust > Crates): > >    In the rust ecosystem it is common for multiple incompatible > ver

Re: Rust freedom issue claim

Ludovic Courtès writes: > Thanks for the detailed study and summary! The conversation about the Rust Trademark policy issue has been happening on several mailing lists and in different IRC channels. I decided to write a new summary that bringing it all together, adds new information and cleans it

Re: Rust freedom issue claim

Leo Famulari writes: > On Sat, Jun 12, 2021 at 02:49:21PM -0400, Bone Baboon wrote: >> Contents: >> * Passive Approaches > > I definitely think a passive approach is best, unless the owners of the > Rust trademark are taking actions that preclude it. Have they given us > any reason to think that w

Re: Rust freedom issue claim

On Sat, Jun 12, 2021 at 02:49:21PM -0400, Bone Baboon wrote: > Contents: > * Passive Approaches I definitely think a passive approach is best, unless the owners of the Rust trademark are taking actions that preclude it. Have they given us any reason to think that we need to do something about this

Re: Rust freedom issue claim

On 2021-06-12, Bone Baboon wrote: > Ludovic Courtès writes: >> Bone Baboon skribis: ... > There are several options for how to move forward with the issue of the > Rust Foundation trademark policy. > > # Passive Approaches ... > * Do nothing > ** Advantages > *** No action needed by Guix. > **

Re: Rust freedom issue claim

Ludovic Courtès writes: > Bone Baboon skribis: > >> After reading further on the topic and receiving feedback I have written >> an update to my understanding of the Rust trademark policy. >> > > Thanks for the detailed st

Re: Rust freedom issue claim

Ludovic Courtès writes: > Before triggering an alarm, I would check what major distros, and Debian > in particular, are doing about Rust; I have not heard of any concerns so > far. If the Rust trademark turns out to be a concern, distros should > try hard, collectively, to resolve it through dialo

Re: Rust freedom issue claim

On Thu, 27 May 2021, Joshua Branson wrote: In terms of languages trying to be replacements for C: - Zig is one of the most famous ones, and will probably be the first C alternatives to reach 1.0. https://ziglang.org/ - Odin https://odin-lang.org/ - scopes which using S-expressions https://

Re: Rust freedom issue claim

Scopes sure looks cool! Pj.

Re: Rust freedom issue claim

Pjotr Prins writes: > On Wed, May 26, 2021 at 04:32:03PM +0200, Ludovic Courtès wrote: >> That’s a somewhat different topic. FWIW, I’m both excited at the idea >> of having a memory-safe replacement for C gaining momentum, and >> frightened by the prospects of Rust being this replacement, for ma

Re: Rust freedom issue claim

Bone Baboon writes: > This is an article from Hyperbola about the Rust trademark. It claims > that Rust has a freedom issue. > > > I searched for this in the Guix bug and devel mailing list archive but > did not see it. > > I wo

Re: Rust freedom issue claim

On Wed, May 26, 2021 at 04:32:03PM +0200, Ludovic Courtès wrote: > That’s a somewhat different topic. FWIW, I’m both excited at the idea > of having a memory-safe replacement for C gaining momentum, and > frightened by the prospects of Rust being this replacement, for many > reasons including: Rus

Re: Rust freedom issue claim

Hi, Bone Baboon skribis: > This is an article from Hyperbola about the Rust trademark. It claims > that Rust has a freedom issue. > (Side note: “freedom issue” is not a helpful term as it could mean all sorts of things.) The

Re: rust-tempfile-3 update to 3.2.0 breaks sequoia build

Hi Nicolas, thanks for the review, Unfortunately I pushed the change just a few minutes ago :-( In `fix-permissions' phase, are you sure you need #o644 permission? Otherwise, you may want to use `make-file-writeable'. Thanks for this tip, I didn't know this function. I'll keep it in mind f

Re: rust-tempfile-3 update to 3.2.0 breaks sequoia build

Hello, Hartmut Goebel writes: > I was able to fix sequoia by updating to 1.1 and applying some more > changes. Thank you. > Please review so we > can get it into upcoming guix 1.3. Thanks in advance I don't use sequoia but I confirm it builds on my x86

Re: rust-tempfile-3 update to 3.2.0 breaks sequoia build

Hi Nicolas, I was able to fix sequoia by updating to 1.1 and applying some more changes. Please review so we can get it into upcoming guix 1.3. Thanks in advance -- Regards Hartmut Goebel | Hartmut Goebel | h.goe...@crazy-compilers.com

Re: rust-tempfile-3 update to 3.2.0 breaks sequoia build

Am 04.04.21 um 11:08 schrieb Nicolas Goaziou: > Not really. Is it possible to upgrade it to a more recent commit? I see > that Cargo.lock references tempfile 3.2.0 in HEAD. The issue is not in tempfile, it's just caused by this update. Thus I'm not confident updating sequoia to a more recent versi

Re: rust-tempfile-3 update to 3.2.0 breaks sequoia build

Hello, Hartmut Goebel writes: > building sequoia is currently broken in master with > "syn::export::ToTokens" not found. > > I tracked this down to 6513650d40f74 "gnu: rust-tempfile-3: Update to > 3.2.0." (2021-02-16). The updated package also updates some > dependency-requirements: cfg-if 0.1 -

Re: Rust and parametric packages

On Sat, 2021-04-03 at 17:47 +0200, Hartmut Goebel wrote: > Am 17.03.21 um 19:23 schrieb Léo Le Bouter: > > I advise you look there also: > > https://rust-lang.zulipchat.com/#narrow/stream/246057-t-cargo/topic/rlib-intermediate-object-reuse/near/225653640 > > Access requires a login. Is there a pu

Re: Rust and parametric packages

Am 17.03.21 um 19:23 schrieb Léo Le Bouter: > I advise you look there also: > https://rust-lang.zulipchat.com/#narrow/stream/246057-t-cargo/topic/rlib-intermediate-object-reuse/near/225653640 Access requires a login. Is there a publicly available mirror? -- Regards Hartmut Goebel | Hartmut Goe

Re: Rust and parametric packages

On Wed, 2021-03-17 at 18:30 +0100, raingloom wrote: > I'm re-reading the threads about Rust packaging and I realized there > might be a solution to the build artifact reuse problem. > > As I understand it, the problem is that crates can be compiled with > any > number of features enabled or disabl

Re: rust (build system) deficits

Hi John, >> This importer does not solve the declarations, and IMHO it should not >> anyway - as the are dependencies of another packages, which might change >> over time. >> > I’m not sure I fully understand why the recursive importer should not > solve the transitive dependencies. Could you elab

Re: rust (build system) deficits

Hi Hartmut, > My point is less the work, but the non-transitive declarations: nettle-sys is an multi-indirect input for sequioa-sqv, still the later needs to specify these dependencies. Totally agree. I think everyone agreed, too. A few months ago we decided that the package inputs should match

Re: rust (build system) deficits

Am 09.03.20 um 15:00 schrieb John Soo: >> - nettle-src, since it is "optional" for nettle-sys - and the phase was >> not executed. >> - bindgen, since it is required to build nettle-sys >> - lalrpop, since it is required for building sequoia-openpgp > > That is a lot of work! […] Also I found the

Re: rust (build system) deficits

Hi Hartmut, > On Mar 9, 2020, at 2:26 AM, Hartmut Goebel > wrote: > A second dependancy is "sequoia-openpgp", which requires rhe lalrpop parser generator for building. Now when building `sequioa-sqv`, I need to add all these dependencies again: - nettle-src, since it is "optional" for nettle

Re: rust (build system) deficits

On Mon, Mar 09, 2020 at 10:26:01AM +0100, Hartmut Goebel wrote: > Am 08.03.20 um 21:10 schrieb John Soo: > > Hmm. Can you elaborate more on “not able to build non-trivial rust > > applications”? > > I'm working on packaging sequoia-openpgp.org. > > This requires nettle-sys, a FFI to nettle. nett

  1   2   >