Conversation

Notices

1. Embed this notice
   mcc (mcc@mastodon.social)'s status on Saturday, 02-Dec-2023 11:26:35 JST mcc

   Sometimes people tell me I have a knack for finding my way into unusually cursed problems.

   • clacke likes this.
   • Ryan Castellucci :nonbinary_flag: repeated this.
   • Embed this notice
     mcc (mcc@mastodon.social)'s status on Saturday, 02-Dec-2023 11:28:34 JST mcc

     in reply to

     • Owen Nelson

     @onelson I did not receive any answers.

   • Embed this notice
     clacke (clacke@libranet.de)'s status on Saturday, 02-Dec-2023 11:28:34 JST clacke

     in reply to

     • Owen Nelson
     @mcc @onelson Wisdom of the Ancients #xkcd979
   • Embed this notice
     Owen Nelson (onelson@mastodon.social)'s status on Saturday, 02-Dec-2023 11:28:35 JST Owen Nelson

     in reply to

     @mcc so hold up. Was there a way?

   • Embed this notice
     mcc (mcc@mastodon.social)'s status on Saturday, 02-Dec-2023 19:56:07 JST mcc

     in reply to

     • nope

     @stacked_automation Oh.

     i d… I don't control the submodule. I control the parent repo and I am including someone else's git repo as a submodule. Does that mean this idea no longer works?

   • Embed this notice
     clacke (clacke@libranet.de)'s status on Saturday, 02-Dec-2023 19:56:07 JST clacke

     in reply to

     • nope
     @mcc @stacked_automation You don't control the submodule, but you could control a directory between the submodule and the project root?
   • Embed this notice
     nope (stacked_automation@mastodon.social)'s status on Saturday, 02-Dec-2023 19:56:08 JST nope

     in reply to

     @mcc my understanding is the workspace would be defined in the submodule, so that when you call cargo *in that submodule*, it will only read submodule/.cargo/config.toml

     similarly, submodule/.cargo/config.toml values take precedence over root/.cargo/config.toml
     so if it were:

     root/.cargo/config.toml::[build] jobs = 2

     that was breaking things, you would override with:

     root/submodule/.cargo/config.toml::[build] jobs = 1

   • Embed this notice
     nope (stacked_automation@mastodon.social)'s status on Saturday, 02-Dec-2023 19:56:09 JST nope

     in reply to

     @mcc you may be able to use workspaces to block it (see link),
     or by explicitly overriding the values messing things up in the submodules config file.

     https://users.rust-lang.org/t/how-to-override-cargo-config-search-order/38197/4

   • Embed this notice
     mcc (mcc@mastodon.social)'s status on Saturday, 02-Dec-2023 19:56:09 JST mcc

     in reply to

     • nope

     @stacked_automation

     1. would using workspaces require moving my src/main.rs to a subdirectory/src/main.rs?
     2. where would the explicit overriding take place? environment variables?

   • Embed this notice
     Erin (chateauerin@mastodon.social)'s status on Saturday, 02-Dec-2023 19:56:13 JST Erin

     in reply to

     @mcc NERDS: with computers, you can do anything you want!
     YOU: can i make the computer not do something that I don't want it to do
     NERDS: >:(

     clacke likes this.
   • Embed this notice
     mcc (mcc@mastodon.social)'s status on Wednesday, 06-Dec-2023 22:01:27 JST mcc

     in reply to

     • clacke
     • nope

     @clacke @stacked_automation I do actually. That's sufficient? Maybe I was confused what was being proposed.

   • Embed this notice
     clacke (clacke@libranet.de)'s status on Wednesday, 06-Dec-2023 22:01:27 JST clacke

     in reply to

     • nope

     @mcc It sounds like there is nothing one can do to stop ancestor traversal, but if a setting in root config messes submodule up, you might be able to revert it in the middle directory?

     @stacked_automation