This repository has been archived by the owner on Jan 8, 2022. It is now read-only.
Why RESTRICT=mirror?
#32
Comments
lo48576
referenced
this issue
in gentoo/guru
Apr 11, 2020
Package-Manager: Portage-2.3.98, Repoman-2.3.22 Signed-off-by: YOSHIOKA Takuma <lo48576@hard-wi.red>
lo48576
referenced
this issue
in gentoo/guru
Apr 11, 2020
Package-Manager: Portage-2.3.98, Repoman-2.3.22 Signed-off-by: YOSHIOKA Takuma <lo48576@hard-wi.red>
lo48576
referenced
this issue
in gentoo/guru
Apr 11, 2020
Package-Manager: Portage-2.3.98, Repoman-2.3.22 Signed-off-by: YOSHIOKA Takuma <lo48576@hard-wi.red>
|
Ok, I understand this exists to prevent portage from fetching crates from mirrors while they are not deployed to mirror servers. |
|
PR is welcome if you'd like to add that boilerplate into every ebuild. |
|
Closing as abandoned. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
cargo-ebuild/src/ebuild.template
Line 18 in 326d33b
Many projects written in Rust are OSS (as far as I know), and
RESTRICT=mirrorseems not necessary for such usual OSS applications, especially when we want ebuild files for them.Why is this line included in default template?
If this exists for safety (i.e. to prevent accidentally mirroring proprietary stuff), then I want some comments in the template to indicate when this line is necessary and when unnecessary.
The text was updated successfully, but these errors were encountered: