Search
1000 results for “Gentoo_eV”
-
If it wasn't enough that we have to keep building new kernels every day and backport vulnerability fixes to older LTS branches, now we also have to deal with upstream doing random backports that are completely broken and never bothering to actually even check if they build.
-
My first ever chinstrap encounter was all I could ever ask for They’re a little uh, feral, as far as penguins go, and this lone chinstrap was running through a Gentoo colony, honking at and chasing after all of its cousins The cutest nightmares #penguin #Antarctica #chinstrap #gentoo #wildlife
-
@peppe well fuck me, I left everything compiling while I eat dinner.
Come back to a black screen yet, the entire PC is still running. Completely unresponsive, nothing seems to be actually working.
So I had to hard reboot, and I am welcome with another black screen.
I have lost patience for today.
-
The previous evening I was doing yet another experiment with safe transition from 32-bit to 64-bit #time_t in #Gentoo. This time I was trying a different approach — rather than changing libdir for the time64 ABI permanently, moving the time32 libraries into a temporary directory for the transition time.
The idea was that we move all old libraries to libt32, and we add RUNPATH to all old binaries to make them capable of finding these libraries. Then, as libraries were rebuilt, Portage would keep old copies in libt32 for as long as they were necessary (through preserved-libs), and then remove them as soon as all reverse dependencies were rebuilt. Unfortunately, even though I hacked hard, I wasn't able to convince Portage to stop treating time64 and time32 libraries as equivalent, and therefore remove the latter immediately after rebuilt.
I was close to thrashing the idea entirely, but near three o'clock in the morning I woke up with another idea — and one much simpler at that. Sure, add RUNPATH to binaries; sure, move the libraries — but without updating the vardb, leaving them out of Portage's control. As packages are rebuilt, Portage will not be removing anything from libt32, and newly built programs, no longer having the RUNPATH injected, would simply stop using libt32 libraries. And when all rebuilds are done, the user can just remove libt32 wholesale.
In the end, it's less work for me (no need to update vdb), and fewer moving parts. What remains is determining which binaries should have their RUNPATHs (already learned the hard way that you can't alter all of them), write a script to inject them and move the libraries, and then try another experiment.
-
One gentoo species, Nope Four
Scientists provided genetic evidence that what was once thought to be one widely dispersed species - including three subspecies - is actually four separate species of gentoo penguin. So, one of these was previously even unrecognised. Because, as it turns out they all look alike: a white underside and black back, but they are clearly genetically different. What scientists refer to as a cryptic species.
#biodiversity #gentoo #penguin #specieshttps://phys.org/news/2026-05-scientists-gentoo-penguins-species-totally.html
-
One gentoo species, Nope Four
Scientists provided genetic evidence that what was once thought to be one widely dispersed species - including three subspecies - is actually four separate species of gentoo penguin. So, one of these was previously even unrecognised. Because, as it turns out they all look alike: a white underside and black back, but they are clearly genetically different. What scientists refer to as a cryptic species.
#biodiversity #gentoo #penguin #specieshttps://phys.org/news/2026-05-scientists-gentoo-penguins-species-totally.html
-
One gentoo species, Nope Four
Scientists provided genetic evidence that what was once thought to be one widely dispersed species - including three subspecies - is actually four separate species of gentoo penguin. So, one of these was previously even unrecognised. Because, as it turns out they all look alike: a white underside and black back, but they are clearly genetically different. What scientists refer to as a cryptic species.
#biodiversity #gentoo #penguin #specieshttps://phys.org/news/2026-05-scientists-gentoo-penguins-species-totally.html
-
One gentoo species, Nope Four
Scientists provided genetic evidence that what was once thought to be one widely dispersed species - including three subspecies - is actually four separate species of gentoo penguin. So, one of these was previously even unrecognised. Because, as it turns out they all look alike: a white underside and black back, but they are clearly genetically different. What scientists refer to as a cryptic species.
#biodiversity #gentoo #penguin #specieshttps://phys.org/news/2026-05-scientists-gentoo-penguins-species-totally.html
-
One gentoo species, Nope Four
Scientists provided genetic evidence that what was once thought to be one widely dispersed species - including three subspecies - is actually four separate species of gentoo penguin. So, one of these was previously even unrecognised. Because, as it turns out they all look alike: a white underside and black back, but they are clearly genetically different. What scientists refer to as a cryptic species.
#biodiversity #gentoo #penguin #specieshttps://phys.org/news/2026-05-scientists-gentoo-penguins-species-totally.html
-
Every time #Emerge by #Fischerspooner comes up in my ears I think of #Gentoo.
> You don’t need to emerge from nothing 🎵
But you kinda do..
-
Our next Speaker Spotlight for #EverythingOpen is Alice Ferrazzi - @alicef - who works with @gentoo.
In this talk, Alice will provide a status update on the #kernelci project.
-
Why Gentoo?
When you think of Gentoo, you tend to think of it being a difficult distribution, where you compile everything yourself.
There’s much more to Gentoo than that. Yes, some of it comes from building from source: the flexibility. But a lot of it comes from the wider Gentoo philosophy, the philosophy that brought us all together. The idea that Gentoo is the distribution we’re making for ourselves and people who enj
-
Testing the CalamaroOS on my old laptop.
For some reason, it sees EVERY single WiFi network around, EXCEPT of 2 networks at the office that I have access to 🙂 Strange.
Other than that, it's just a #gentoo
--- building package 25 of 27 - media-video/vlc
-
So #Gentoo #Python eclasses are pretty modern, in the sense that they tend to follow the best practices and standards, and eventually deal with deprecations. Nevertheless, they have a long history and carry quite some historical burden, particularly regarding to naming.
The key point is that the eclasses were conceived as a replacement for the old eclasses: "distutils" and "python". Hence, much like we revision ebuilds, I've named the matching eclasses "distutils-r1" and "python-r1". For consistency, I've also used the "-r1" suffix for the remaining eclasses introduced at the time: "python-any-r1", "python-single-r1" and "python-utils-r1" — even though there were never "r0"s.
It didn't take long to realize my first mistake. I've made the multi-impl eclass effectively the "main" eclass, probably largely inspired by the previous Gentoo recommendations. However, in the end I've found out that for the most use cases (i.e. where "distutils-r1" is not involved), there is no real need for multi-impl, and it makes things much harder. So if I were naming them today, I would have named it "python-multi", to indicate the specific use case — and either avoid designating a default at all, or made "python-single" the default.
What aged even worse is the "distutils-r1" eclass. Admittedly, back when it was conceived, distutils was still largely a thing — and there were people (like me) who avoided unnecessary dependency on setuptools. Of course, nowadays it has been entirely devoured by setuptools, and with #PEP517 even "setuptools" wouldn't be a good name anymore. Nowadays, people are getting confused why they are supposed to use "distutils-r1" for, say, Hatchling.
Admittedly, this is something I could have done differently — PEP517 support was a major migration, and involved an explicit switch. Instead of adding DISTUTILS_USE_PEP517 (what a self-contradictory name) variable, I could have forked the eclass. Why didn't I do that? Because there used to be a lot of code shared between the two paths. Of course, over time they diverged more, and eventually I've dropped the legacy support — but the opportunity to rename was lost.
In fact, as a semi-related fact, I've recognized another design problem with the eclass earlier — I should have gone for two eclasses rather than one: a "python-phase" eclass with generic sub-phase support, and a "distutils" (or later "python-pep517") implementing default sub-phases for the common backends. And again, this is precisely how I could have solved the code reuse problem when I introduced PEP517 support.
But then, I didn't anticipate how the eclasses would end up looking like in the end — and I can't really predict what new challenges the Python ecosystem is going to bring us. And I think it's too late to rename or split stuff — too much busywork on everyone.
-
So #Gentoo #Python eclasses are pretty modern, in the sense that they tend to follow the best practices and standards, and eventually deal with deprecations. Nevertheless, they have a long history and carry quite some historical burden, particularly regarding to naming.
The key point is that the eclasses were conceived as a replacement for the old eclasses: "distutils" and "python". Hence, much like we revision ebuilds, I've named the matching eclasses "distutils-r1" and "python-r1". For consistency, I've also used the "-r1" suffix for the remaining eclasses introduced at the time: "python-any-r1", "python-single-r1" and "python-utils-r1" — even though there were never "r0"s.
It didn't take long to realize my first mistake. I've made the multi-impl eclass effectively the "main" eclass, probably largely inspired by the previous Gentoo recommendations. However, in the end I've found out that for the most use cases (i.e. where "distutils-r1" is not involved), there is no real need for multi-impl, and it makes things much harder. So if I were naming them today, I would have named it "python-multi", to indicate the specific use case — and either avoid designating a default at all, or made "python-single" the default.
What aged even worse is the "distutils-r1" eclass. Admittedly, back when it was conceived, distutils was still largely a thing — and there were people (like me) who avoided unnecessary dependency on setuptools. Of course, nowadays it has been entirely devoured by setuptools, and with #PEP517 even "setuptools" wouldn't be a good name anymore. Nowadays, people are getting confused why they are supposed to use "distutils-r1" for, say, Hatchling.
Admittedly, this is something I could have done differently — PEP517 support was a major migration, and involved an explicit switch. Instead of adding DISTUTILS_USE_PEP517 (what a self-contradictory name) variable, I could have forked the eclass. Why didn't I do that? Because there used to be a lot of code shared between the two paths. Of course, over time they diverged more, and eventually I've dropped the legacy support — but the opportunity to rename was lost.
In fact, as a semi-related fact, I've recognized another design problem with the eclass earlier — I should have gone for two eclasses rather than one: a "python-phase" eclass with generic sub-phase support, and a "distutils" (or later "python-pep517") implementing default sub-phases for the common backends. And again, this is precisely how I could have solved the code reuse problem when I introduced PEP517 support.
But then, I didn't anticipate how the eclasses would end up looking like in the end — and I can't really predict what new challenges the Python ecosystem is going to bring us. And I think it's too late to rename or split stuff — too much busywork on everyone.
-
So #Gentoo #Python eclasses are pretty modern, in the sense that they tend to follow the best practices and standards, and eventually deal with deprecations. Nevertheless, they have a long history and carry quite some historical burden, particularly regarding to naming.
The key point is that the eclasses were conceived as a replacement for the old eclasses: "distutils" and "python". Hence, much like we revision ebuilds, I've named the matching eclasses "distutils-r1" and "python-r1". For consistency, I've also used the "-r1" suffix for the remaining eclasses introduced at the time: "python-any-r1", "python-single-r1" and "python-utils-r1" — even though there were never "r0"s.
It didn't take long to realize my first mistake. I've made the multi-impl eclass effectively the "main" eclass, probably largely inspired by the previous Gentoo recommendations. However, in the end I've found out that for the most use cases (i.e. where "distutils-r1" is not involved), there is no real need for multi-impl, and it makes things much harder. So if I were naming them today, I would have named it "python-multi", to indicate the specific use case — and either avoid designating a default at all, or made "python-single" the default.
What aged even worse is the "distutils-r1" eclass. Admittedly, back when it was conceived, distutils was still largely a thing — and there were people (like me) who avoided unnecessary dependency on setuptools. Of course, nowadays it has been entirely devoured by setuptools, and with #PEP517 even "setuptools" wouldn't be a good name anymore. Nowadays, people are getting confused why they are supposed to use "distutils-r1" for, say, Hatchling.
Admittedly, this is something I could have done differently — PEP517 support was a major migration, and involved an explicit switch. Instead of adding DISTUTILS_USE_PEP517 (what a self-contradictory name) variable, I could have forked the eclass. Why didn't I do that? Because there used to be a lot of code shared between the two paths. Of course, over time they diverged more, and eventually I've dropped the legacy support — but the opportunity to rename was lost.
In fact, as a semi-related fact, I've recognized another design problem with the eclass earlier — I should have gone for two eclasses rather than one: a "python-phase" eclass with generic sub-phase support, and a "distutils" (or later "python-pep517") implementing default sub-phases for the common backends. And again, this is precisely how I could have solved the code reuse problem when I introduced PEP517 support.
But then, I didn't anticipate how the eclasses would end up looking like in the end — and I can't really predict what new challenges the Python ecosystem is going to bring us. And I think it's too late to rename or split stuff — too much busywork on everyone.
-
So #Gentoo #Python eclasses are pretty modern, in the sense that they tend to follow the best practices and standards, and eventually deal with deprecations. Nevertheless, they have a long history and carry quite some historical burden, particularly regarding to naming.
The key point is that the eclasses were conceived as a replacement for the old eclasses: "distutils" and "python". Hence, much like we revision ebuilds, I've named the matching eclasses "distutils-r1" and "python-r1". For consistency, I've also used the "-r1" suffix for the remaining eclasses introduced at the time: "python-any-r1", "python-single-r1" and "python-utils-r1" — even though there were never "r0"s.
It didn't take long to realize my first mistake. I've made the multi-impl eclass effectively the "main" eclass, probably largely inspired by the previous Gentoo recommendations. However, in the end I've found out that for the most use cases (i.e. where "distutils-r1" is not involved), there is no real need for multi-impl, and it makes things much harder. So if I were naming them today, I would have named it "python-multi", to indicate the specific use case — and either avoid designating a default at all, or made "python-single" the default.
What aged even worse is the "distutils-r1" eclass. Admittedly, back when it was conceived, distutils was still largely a thing — and there were people (like me) who avoided unnecessary dependency on setuptools. Of course, nowadays it has been entirely devoured by setuptools, and with #PEP517 even "setuptools" wouldn't be a good name anymore. Nowadays, people are getting confused why they are supposed to use "distutils-r1" for, say, Hatchling.
Admittedly, this is something I could have done differently — PEP517 support was a major migration, and involved an explicit switch. Instead of adding DISTUTILS_USE_PEP517 (what a self-contradictory name) variable, I could have forked the eclass. Why didn't I do that? Because there used to be a lot of code shared between the two paths. Of course, over time they diverged more, and eventually I've dropped the legacy support — but the opportunity to rename was lost.
In fact, as a semi-related fact, I've recognized another design problem with the eclass earlier — I should have gone for two eclasses rather than one: a "python-phase" eclass with generic sub-phase support, and a "distutils" (or later "python-pep517") implementing default sub-phases for the common backends. And again, this is precisely how I could have solved the code reuse problem when I introduced PEP517 support.
But then, I didn't anticipate how the eclasses would end up looking like in the end — and I can't really predict what new challenges the Python ecosystem is going to bring us. And I think it's too late to rename or split stuff — too much busywork on everyone.
-
For years I've upgrade my #Gentoo kernel by running
> make oldconfig
> make && make modules && make modules_installLater in the process, I use #GenKernel to create and put everything in /boot.
I've had no problems with this, but I've long wondered if it is technically an okay way to do it? Would it be better to use genkernel for everything? Or hand create the boot stuff?
-
The couple’s fame drew local & international tourists, who watched them waddle around their home in the aquarium on Sydney’s docks. Unusually for #gentoo #penguin couples, the aquarium said, the pair were so close they even spent time together outside of breeding season. After spending more than half his life w/ his partner, #Magic will now face his first breeding season without #Sphen, said Richard Dilly, general manager at #Sea Life #Sydney Aquarium.
-
The couple’s fame drew local & international tourists, who watched them waddle around their home in the aquarium on Sydney’s docks. Unusually for #gentoo #penguin couples, the aquarium said, the pair were so close they even spent time together outside of breeding season. After spending more than half his life w/ his partner, #Magic will now face his first breeding season without #Sphen, said Richard Dilly, general manager at #Sea Life #Sydney Aquarium.
-
The couple’s fame drew local & international tourists, who watched them waddle around their home in the aquarium on Sydney’s docks. Unusually for #gentoo #penguin couples, the aquarium said, the pair were so close they even spent time together outside of breeding season. After spending more than half his life w/ his partner, #Magic will now face his first breeding season without #Sphen, said Richard Dilly, general manager at #Sea Life #Sydney Aquarium.
-
The couple’s fame drew local & international tourists, who watched them waddle around their home in the aquarium on Sydney’s docks. Unusually for #gentoo #penguin couples, the aquarium said, the pair were so close they even spent time together outside of breeding season. After spending more than half his life w/ his partner, #Magic will now face his first breeding season without #Sphen, said Richard Dilly, general manager at #Sea Life #Sydney Aquarium.
-
#Gentoo #Linux Begins Offering #x86-64-v3 Binary Packages
Gentoo is joining the likes of Serpent OS, RHEL 10, Ubuntu and other Linux distributions that are optionally providing #x86_64_v3 packages or currently exploring the possibilities of doing so or even raising their #x86_64 baseline in the future.
https://www.phoronix.com/news/Gentoo-x86-64-v3-Binaries -
Did I ever mention that since xz-utils 5.4.0+ supports decompressing .lz files? Since the two formats are very similar, we could get #xz to support the other format with minimal overhead, and save you from having to use two tools!
Why is this important? Because it means that you can now use the superior #lzip format without having to worry that your users will have to install lzip to unpack them! Unpacker.eclass #Gentoo is already taking advantage of that.
-
CW: Computer programming on :gentoo:
I have hacked out a #Gentoo ebuild for the Oxford #Oberon2 Compiler:
chemoelectric / chemoelectric-overlay / dev-lang / obc — Bitbucket https://bitbucket.org/chemoelectric/chemoelectric-overlay/src/master/dev-lang/obc/
For the #RosettaCode buffs who program in all the languages except those they hate, and sometimes even in those they hate.
-
CW: Computer programming on :gentoo:
I have hacked out a #Gentoo ebuild for the Oxford #Oberon2 Compiler:
chemoelectric / chemoelectric-overlay / dev-lang / obc — Bitbucket https://bitbucket.org/chemoelectric/chemoelectric-overlay/src/master/dev-lang/obc/
For the #RosettaCode buffs who program in all the languages except those they hate, and sometimes even in those they hate.
-
CW: Computer programming on :gentoo:
I have hacked out a #Gentoo ebuild for the Oxford #Oberon2 Compiler:
chemoelectric / chemoelectric-overlay / dev-lang / obc — Bitbucket https://bitbucket.org/chemoelectric/chemoelectric-overlay/src/master/dev-lang/obc/
For the #RosettaCode buffs who program in all the languages except those they hate, and sometimes even in those they hate.
-
@Evv1L Откуда такая информация?
https://en.wikipedia.org/wiki/Joaquin_Phoenix Ctrl+F gentoo — ничего не найдено. Также Qwant не нашёл ничего подходящего по запросу «Хоакин Феникс несколько дней ставил Gentoo» (без кавычек).P. S. Восхищён Вашим упорством. Надеюсь, у Вас получится.
#Wikipedia #Википедия #Gentoo #Генту #Quant #JoaquinPhoenix #ХоакинФеникс
-
Alright new instance new #introduction time. I should really just copy this somewhere so I don't have to keep retyping it, given how much I move.
I'm #queer, and #polyamorous who's about 30 years old at the time of writing. I do tend to hop around fediverse instances, but I'd like to stop that at some point. I liked Friendica a lot, but my last 2 instances died very suddenly, and I decided against trying a third time. My more stationary account is @[email protected], which should be up indefinitely if I don't decide to stop giving omg.lol my money (unlikely, they deserve it!)
I'm a #gamer, and have been for as long as I can remember. I play #FinalFantasyXIV, #GuildWars2, and #WurmOnline for #MMORPG, and I rotate between a few different non MMOs. I tend to play a lot of #VisualNovel, #Mahjong on Riichi City (and hopefully some on FFXIV once cross-DC queues hit NA!), and a lot of #NSFW games. If you have any suggestions on those don't hesitate to DM me, I'm always looking for more!
For some technical hobbies, I'm into #3DPrinting, and I've dabbled in #Soldering to make my own #MechanicalKeyboard. Didn't design it, but I did put it together without a kit :D
Generally I'm very into #FOSS, and #HomeLab. I've also been a #Linux user since 2010. Over the years I've used several flavors of Ubuntu, Debian, EndeavourOS, Garuda Linux, Arch Linux, and currently a #Gentoo user. Also #Emacs is the best piece of software to ever be released.
I'm a #Writer, though I'm currently being very slow writing this novella. Hoping to turn it into a VN, but I can't draw to save my life, and it's real expensive to commission that many images. Might just do a light novel-style thing and throw an image in with each chapter.
For crafts I like #Knitting, and I can #Crochet though do that very infrequently because it hurts. I also do #TabletWeaving, though I'm fairly new at that.
That's just about everything! I do occasionally boost porn, and will probably post my own at some point. Images will be CW'd, text likely will not be, as it causes some distress figuring out what to CW -
Alright new instance new #introduction time. I should really just copy this somewhere so I don't have to keep retyping it, given how much I move.
I'm #queer, and #polyamorous who's about 30 years old at the time of writing. I do tend to hop around fediverse instances, but I'd like to stop that at some point. I liked Friendica a lot, but my last 2 instances died very suddenly, and I decided against trying a third time. My more stationary account is @[email protected], which should be up indefinitely if I don't decide to stop giving omg.lol my money (unlikely, they deserve it!)
I'm a #gamer, and have been for as long as I can remember. I play #FinalFantasyXIV, #GuildWars2, and #WurmOnline for #MMORPG, and I rotate between a few different non MMOs. I tend to play a lot of #VisualNovel, #Mahjong on Riichi City (and hopefully some on FFXIV once cross-DC queues hit NA!), and a lot of #NSFW games. If you have any suggestions on those don't hesitate to DM me, I'm always looking for more!
For some technical hobbies, I'm into #3DPrinting, and I've dabbled in #Soldering to make my own #MechanicalKeyboard. Didn't design it, but I did put it together without a kit :D
Generally I'm very into #FOSS, and #HomeLab. I've also been a #Linux user since 2010. Over the years I've used several flavors of Ubuntu, Debian, EndeavourOS, Garuda Linux, Arch Linux, and currently a #Gentoo user. Also #Emacs is the best piece of software to ever be released.
I'm a #Writer, though I'm currently being very slow writing this novella. Hoping to turn it into a VN, but I can't draw to save my life, and it's real expensive to commission that many images. Might just do a light novel-style thing and throw an image in with each chapter.
For crafts I like #Knitting, and I can #Crochet though do that very infrequently because it hurts. I also do #TabletWeaving, though I'm fairly new at that.
That's just about everything! I do occasionally boost porn, and will probably post my own at some point. Images will be CW'd, text likely will not be, as it causes some distress figuring out what to CW