Date: Fri, 23 Sep 2022 19:44:41 +0000 From: bugzilla-noreply@freebsd.org To: doc@FreeBSD.org Subject: [Bug 266571] Porter's Handbook: Using cargo: Use Makefile.crates instead of Makefile's CARGO_CRATES Message-ID: <bug-266571-9@https.bugs.freebsd.org/bugzilla/>
index | next in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266571 Bug ID: 266571 Summary: Porter's Handbook: Using cargo: Use Makefile.crates instead of Makefile's CARGO_CRATES Product: Documentation Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: Books & Articles Assignee: doc@FreeBSD.org Reporter: eduardo@FreeBSD.org Hello, For some time that Mk/Uses/cargo.mk (.sinclude "${MASTERDIR}/Makefile.crates") permits using Makefile.crates instead of Makefile to include list of cargo-crates. This feature has the advantage of having cleaner Makefile and easier updates with `make cargo-crates > Makefile.crates`. For what I see, only a few maintainers know about this "hiden" ports framework feature. What I propose is to change methodology of rust/cargo ports to include Makefile.crates. As an example, we have Makefile PLIST_FILES against pkg-plist and it's very well explained: "There is only one case when pkg-plist can be omitted from a port. If the port installs just a handful of files, list them in PLIST_FILES, within the port’s Makefile. (...)" The same could be adapted to Makefile.crates (if/when methodology gets updated): "There is only one case when Makefile.crates can be omitted from a port. If the port uses just a handful of cargo crates, list them in CARGO_CRATES, within the port’s Makefile. (...)" Thanks -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-266571-9>