Gentoo was my very first distro and the handbook taught me tons in a very short period of time. It took a few days as I was also reading the entire handbook at the same time, but it was well worth it. I'm still using the same install from 2002 that started on an SATA HD, and now resides on an NVMe; Never had to do a fresh/re-install...I always managed to find a way to fix anything I broke, which was a lot.
I’m just getting started with Gentoo. I’ve used Linux since the early 2000s and I’m comfortable on the cli. This video along with others I see on your channel are going to make my Gentoo journey so much easier. Thank you so much! ❤👏
Just a heads up to anyone new viewing this video. euses is deprecated or unmaintained so stick with equery u that will provide all uses flags and their description for the pkg
last time i used gentoo i got confused with these little things like masked packages, but now i think i will try it once again as things have become a little clearer now. great stuff keep making videos like this...👍
Idk if anyone mentioned this. Its not something that really matters much, but is just good info i think. When you are installing a package froma binary distro. They don't actually have all features built into them. Some packages might, others won't and the maintainer decided which options to enable or disable. The main thing is what you said though. Which is true. You don't get any choice on what is included. Unless you go and compile the package yourself with that option enabled or disabled.
19:42 - masking... there are 3 types of masking. License, Arch, and Explicit masking. An example of a license-masked ebuild is app-arch/unrar. It requires you to add unRAR to your package.license. Arch masking is usually used for testing and unstable packages. This can be ~arch masking as is the case with, say, wine-vanilla-currentversion, or ** masking as is the case with wine-vanilla-9999 (or any other git repo ebuilds) Explicit masking is used on very few official ebuilds. I'm fairly certain it's only if the ebuild has some sort of MAJOR security concern. Explicitly masked packages can be unmasked at your peril using package.unmask, and non-masked packages can be explicitly masked using package.mask.
20:50 - they used to be files. If I'm not mistaken, you can still have them as files, but emerge will complain as this is deprecated. Not to mention file bloat. I usually have my files as package.whatever/package-category, so, for example, I have a file app-emulation under package.accept_keywords, and a file app-arch under package.license.
you can use the version numbers in the accept_keywords/ file, you just need an equal sign (or equal greater) sign in from of the package atom name. That way you will unmask the specific version! Or, you just remove the version suffix and unmask the package globally. EDIT: you have covered this later in video :)
18:11 you should not do this, you essentially installing unstable libraries on stable branch, eventually your system will be broken. The solution if you really need that package is to enable global unstable ~amd64 branch in make conf and rebuild the system. Or use other package managers wich are not distro specific - nix package manager, flatpak, distrobox.
Very usefull information, thank you very much! Regarding the "package.accept_keywords" directory (or "package.use"), could you regroup all your individual files under one unique file (including all your conditions for all your packages under one unique file)?
yeah as long as they are in there respective directories.. meaning if you wanted to only have 1 file in package.use or 1 file in package.accept_keywords then you can.. only reason I chose not to do it is because I thought my way was cleaner but truth is theres no real clean solution... either you have a giant ass file or you have many different ones
it just means "look in the current directory" for this specific file or specific directory.. www.theserverside.com/blog/Coffee-Talk-Java-News-Stories-and-Opinions/Why-must-you-use-to-run-your-Ubuntu-scripts-The-meaning-of-Linuxs-dot-slash-explained
11:30 interesting, you have "X" in global USE flags, but when you emerged links, it was "-X". Also links had no GUI, but it somehow was compiled with jpeg support.
I think if you have package.use USE flag set.. it takes precedence over whats in make.conf.. thats why I could have X in make.conf but -X in package.use/links
I don't use gentoo and it is very unlikely that I will because I don't have that much time to do it, but I am someone who is open to knowledge and I am always willing to learn new things (and at the same time to know why femboys like it so much XD)
@@JamesSmith-ix5jd too be honest it’s habit, but I do prefer direct paths names then having the shell guess which files I want. It’s just something I’ve always done
@linuxtechgeek It is still kind of relative filename, "." just expands to current directory. Absolute filename always starts with "/" I see some possible pitfalls in which you can fall with such a habit. First of all is doing some action on "./" Itself, because you are used to type it, one day you can do some mistake in a lengthy command and pass ./ Into it without your intended target. "." and ".." as well as "*" and quotes " should be used with extreme caution on the command line. They are giving most problems for most people, if every command you run has to be run with caution none of them will, you are setting yourself up for a big mistake in the future. When I see ./ , ../ , * or " " in my command I always check it two times and wait 2 seconds before hitting enter. I made some mistakes in the past, like rm -rf .* Instead of rm -rf ./* which deleted not only everything inside the current directory, but also ".." without me realizing it, I don't think it went to the upper directly thanks god. Anyway, just be careful, when something expands it's easier to not catch the mistake in time.
Gentoo was my very first distro and the handbook taught me tons in a very short period of time. It took a few days as I was also reading the entire handbook at the same time, but it was well worth it.
I'm still using the same install from 2002 that started on an SATA HD, and now resides on an NVMe; Never had to do a fresh/re-install...I always managed to find a way to fix anything I broke, which was a lot.
Yep, it just works
Wow, that is pretty incredible!
No way this guy's gentoo installation is older than me
I’m just getting started with Gentoo. I’ve used Linux since the early 2000s and I’m comfortable on the cli. This video along with others I see on your channel are going to make my Gentoo journey so much easier. Thank you so much! ❤👏
Awesome. I’m glad it could help
Just a heads up to anyone new viewing this video. euses is deprecated or unmaintained so stick with equery u that will provide all uses flags and their description for the pkg
Is it possible to install Gentoo with 0 systemD dependency?
I am on the verge to install Gentoo for the first time, this was a very nice video to watch.
That’s awesome, if you’re nervous about it or not 100% sure on the documentation then I recommend doing it in a virtual machine first. Good luck
last time i used gentoo i got confused with these little things like masked packages, but now i think i will try it once again as things have become a little clearer now. great stuff keep making videos like this...👍
Yeah it takes a bit to get used too
Idk if anyone mentioned this. Its not something that really matters much, but is just good info i think.
When you are installing a package froma binary distro. They don't actually have all features built into them. Some packages might, others won't and the maintainer decided which options to enable or disable.
The main thing is what you said though. Which is true. You don't get any choice on what is included. Unless you go and compile the package yourself with that option enabled or disabled.
@@_BLANK_BLANK yeah valid point. I probably forgot to mention that during that time.
Awesome video. Thanks, I just started my gentoo adventure.
19:42 - masking... there are 3 types of masking. License, Arch, and Explicit masking.
An example of a license-masked ebuild is app-arch/unrar. It requires you to add unRAR to your package.license.
Arch masking is usually used for testing and unstable packages. This can be ~arch masking as is the case with, say, wine-vanilla-currentversion, or ** masking as is the case with wine-vanilla-9999 (or any other git repo ebuilds)
Explicit masking is used on very few official ebuilds. I'm fairly certain it's only if the ebuild has some sort of MAJOR security concern. Explicitly masked packages can be unmasked at your peril using package.unmask, and non-masked packages can be explicitly masked using package.mask.
yeah video was like two years ago, I prob have a better understanding of it now but thanks
20:50 - they used to be files. If I'm not mistaken, you can still have them as files, but emerge will complain as this is deprecated. Not to mention file bloat. I usually have my files as package.whatever/package-category, so, for example, I have a file app-emulation under package.accept_keywords, and a file app-arch under package.license.
nice
you can use the version numbers in the accept_keywords/ file, you just need an equal sign (or equal greater) sign in from of the package atom name. That way you will unmask the specific version! Or, you just remove the version suffix and unmask the package globally. EDIT: you have covered this later in video :)
Yeah lol
🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥
Thank you
18:11 you should not do this, you essentially installing unstable libraries on stable branch, eventually your system will be broken. The solution if you really need that package is to enable global unstable ~amd64 branch in make conf and rebuild the system. Or use other package managers wich are not distro specific - nix package manager, flatpak, distrobox.
May I humbly offer the suggestion of using Herbsluftwm. Easy to use and configure
Very usefull information, thank you very much!
Regarding the "package.accept_keywords" directory (or "package.use"), could you regroup all your individual files under one unique file (including all your conditions for all your packages under one unique file)?
yeah as long as they are in there respective directories.. meaning if you wanted to only have 1 file in package.use or 1 file in package.accept_keywords then you can.. only reason I chose not to do it is because I thought my way was cleaner but truth is theres no real clean solution... either you have a giant ass file or you have many different ones
I love Gentoo! But one honest question here, how much time it takes you to compile firefox?
Not long because I use the binary package for it. I’ve never compiled the browser from source
~4-5 hours. Not the best computer -j4 i5 4460 8GB RAM
why do you put ./ before directories and files?
it just means "look in the current directory" for this specific file or specific directory..
www.theserverside.com/blog/Coffee-Talk-Java-News-Stories-and-Opinions/Why-must-you-use-to-run-your-Ubuntu-scripts-The-meaning-of-Linuxs-dot-slash-explained
thats a pretty good article on why to use it
thank you.
Quick question, what WM are you using?
In this video I was using Qtile, but I usually switch between Qtile and DWM.. depends on the day
11:30 interesting, you have "X" in global USE flags, but when you emerged links, it was "-X". Also links had no GUI, but it somehow was compiled with jpeg support.
I think if you have package.use USE flag set.. it takes precedence over whats in make.conf.. thats why I could have X in make.conf but -X in package.use/links
I don't use gentoo and it is very unlikely that I will because I don't have that much time to do it, but I am someone who is open to knowledge and I am always willing to learn new things (and at the same time to know why femboys like it so much XD)
Yeah its always great to learn new things and appreciate them even if your not going to use that "THING" yourself.
gentoo now have binarys and you can choose
Yeah, that video was WAY before binary support became a thing, but you are right
Why are you always typing ./ for every file, it is not necessary for non executables.
@@JamesSmith-ix5jd too be honest it’s habit, but I do prefer direct paths names then having the shell guess which files I want. It’s just something I’ve always done
@linuxtechgeek It is still kind of relative filename, "." just expands to current directory. Absolute filename always starts with "/"
I see some possible pitfalls in which you can fall with such a habit. First of all is doing some action on "./" Itself, because you are used to type it, one day you can do some mistake in a lengthy command and pass ./ Into it without your intended target.
"." and ".." as well as "*" and quotes " should be used with extreme caution on the command line. They are giving most problems for most people, if every command you run has to be run with caution none of them will, you are setting yourself up for a big mistake in the future.
When I see ./ , ../ , * or " " in my command I always check it two times and wait 2 seconds before hitting enter. I made some mistakes in the past, like rm -rf .* Instead of rm -rf ./* which deleted not only everything inside the current directory, but also ".." without me realizing it, I don't think it went to the upper directly thanks god. Anyway, just be careful, when something expands it's easier to not catch the mistake in time.