Talk:Kernel Deblobing

From Gentoo Wiki
Jump to:navigation Jump to:search
This is a Talk page - please see the documentation about using talk pages. Add newer comments below older ones, sign comments using four tildes (~~~~), and indent successive comments with colons (:). Add new sections at the bottom of the page, under a heading (== ==). Please remember to mark sections as "open for discussion" using {{talk|open}}, so they will show up in the list of open discussions.

Setting Python version

Talk status
This discussion is done.

I don't really like changing my favorite Python version with eselect globally. What about running the deblob script in the following way?

root #PYTHON="python2.7" ./deblob-4.11

--Fturco (talk) 13:12, 26 June 2017 (UTC)

Of course, feel free to change the page content if you tested this solution (I'll try it at my next deblob run). Making two eselect python set if needed, before and after deblobing, isn't such a big work…
Francoisd (talk) 16:22, 26 June 2017 (UTC)
Fturco (talk) 19:18, 27 June 2017 (UTC)
Fturco, I don't agree with your deletion of the eselect solution, it would be better to add the second (and very good) one: Gentoo's philosophy is to provide choices to users, then they choose the solution they prefer. The 1st solution indicates if Python 2.7 is installed, the 2nd one needs an emerge even if Python 2.7 is installed and is the favorite version.
Francoisd (talk) 11:01, 28 June 2017 (UTC)
My solution doesn't require the user to re-emerge python:2.7 if it already installed because of the --noreplace option. Changing the default Python interpreter with eselect may break other applications if you forget to restore the initial settings. My solution instead is limited to the deblob script only, and it is easier because it requires just one command instead of two. Fturco (talk) 09:58, 29 June 2017 (UTC)