supakeen

Mmm, COPR and Koji I think use the same mock configs but someone else would have to confirm that :)

It's definitely possible that one of a packages build dependencies pulls in something that a package /should/ depend on and then when it drops it suddenly the build fails. That's why I think we mostly want 'autogenerated' BuildRequires nowadays that are generated based on the upstream source or packaging format to make that less of a figuring out excercise.

I mean; this is the normal mode of operation for GitHub at this point.

It would probably be a good idea to verify some of the ideas you're posting; some of them are oversimplified (or wrong) :)

Ah yea then I misunderstood. That's right you can't easily switch out the cells for protected cells yourself :(

Sure, that means the idea of using unprotected cells was already there when the holders were selected :)

Thanks, fixed!

Thanks, I've written that one down in my notes as well it definitely fits the superstitions because it sounds like it should work well.

Yea, it's not super clear but that's indeed what I meant to say :)

The activation of the virtualenv is unnecessary (one can execute pip/python directly from it), and the configuring of your local pyenv interpreter is also unnecessary, it can create a virtual environment with one directly:

  pyenv virtualenv python3.12 .venv
  .venv/bin/python -m pip install pandas
  .venv/bin/python

Not quite one command, but a bit more streamlined; I guess.

Betteridge's law applies:

> Any headline that ends in a question mark can be answered by the word no."

No, it looks different from this.