dutch-master reacted to drobbins in The Funtoo Way
I have updated our Development Guide to contain information on the "Funtoo Way". The "Funtoo Way" is a really important philosophy about how we do things at Funtoo and I strongly encourage everyone to read it, even if you don't consider yourself a "developer". It helps to explain how our community works and how we can work together.
dutch-master reacted to cardinal in Package libvpx masked, prevents Mate installation
>=libvpx-1.8.0 globally masked you could disable vpx use flag globally in /etc/portage/make.conf to eliminate any need for libvpx.
I need vpx for ffmpeg and it was preventing the x265 update.
I comment out the mask which is temporary which allowed the update to proceed.
rj@funtoo /var/git/meta-repo/kits/core-kit/profiles/package.mask $ sudo nano funtoo-cautionary # Allow firefox to merge cleanly #>=media-libs/libvpx-1.8 You could also add the libvpx-1.7.0.ebuild from the 1.3-release branch to a local overlay.
dutch-master reacted to calrama in Funtoo is now on Discord
(Quote emphasis mine)
That may be the case from your perspective and that's perfectly fine. The reason why I made a sad reaction to the announcement (and the update) is because mine is different.
To the best of my knowledge Discord requires sending all your voice data to their servers with only transport encryption, not end-to-end, so there's no reason to believe they aren't storing it. If you think conventional data breaches are dangerous, consider what would happen if a criminal element got access to a vast amount of such voice data (impersonation being only the most obvious one). You may call me paranoid, but in recent times this risk is unacceptable to me.
My personal issue with Telegram is one of trust in their technology. MTProto 1's numerous unexplained oddities are well known and haven't all been addressed in version 2. This, combined with the fact that the principal mind behind their design is not a cryptographer, marks Telegram as "do not touch with a ten foot pole" for me.
Don't get me wrong, I generally love shiny new technology and I do recognize the immense convenience both of these tools have for a vast amount of people, but I will not use something just because it's shiny and more convenient for other people. It also needs to not be a regression from existing technology for me, which both of these two tools are.
I'm happy in the sense that more people are likely to join the Funtoo community. I'm sad that it had to be these two technologies, for the reasons I mentioned.
dutch-master reacted to paddymac in Do I need to file a bug, or am I just being a nuisance?
Funtoo is my favorite Linux distro. I've been using it enthusiastically since at least 2012. I've been tinkering a lot with FreeBSD for the past 3 years which has divided my attention, but I still use Funtoo as my primary desktop OS.
Here's my concern. I'm using Funtoo 1.2. In the past few months, I've encountered a LOT of blockers when trying to emerge world. Sometimes the blockers are things that don't exist in the portage tree, sometimes they are things which need to be unmasked, and sometimes they are things which need to be unmasked by keyword. I went through a short period of time where I filed a lot of bugs about these blockers. But one bug I filed was dismissed as a "workaround" because I filed a bug about something which needed to be unmasked.
My feeling on the matter is that, if I try to emerge a package that it unmasked by default, then it should emerge without any problem. It should NOT require me to unmask anything or unmask something by keyword. Only ebuilds which are themselves masked or keyworded should rely on other ebuilds which are masked or keyworded. That's my opinion, but if that is not the opinion of the Funtoo project, I ask that such opinions be made plain so that people like me who love the project and want to contribute do not become nuisances by filing bugs or complaining when that is not the goal of the project. But at the same time, if that is not the goal of the project, then why are such bug reports being closed as "workaround" instead of being properly fixed? I asked Daniel and the rest of the Funtoo devs to please make a clear statement about these sorts of things so that users like me who are trying to help can be a genuine help without being a nuisance.