/me bashes you with clubsbakaohki wrote:Deeply agree with the original post, too bad that eight out of ten Gentooists are a "bit" sensitive to criticism. Now bash me with clubs please.
Your welcome.
It does not. It contains no mechanism to cleanly uninstall modularized subsystem. And this is the major task the packaging system/distribution should excel at.Headrush wrote: The meta-packaging system works fine, just because it doesn't work with ~arch doesn't mean it doesn't work.
There are several posts already that show you a simple BASH script to add all the entries for you into /etc/portage/package.keywords.
Technically the meta packages aren't even packages and need not be in portage. The devs just through them in there for convenience of those people who wanted every package like with the monolithic package. (Who the hell uses every single KDE app in each meta anyways?dmpogo wrote:It does not. It contains no mechanism to cleanly uninstall modularized subsystem. And this is the major task the packaging system/distribution should excel at.Headrush wrote: The meta-packaging system works fine, just because it doesn't work with ~arch doesn't mean it doesn't work.
There are several posts already that show you a simple BASH script to add all the entries for you into /etc/portage/package.keywords.
Not sure what you are saying.dmpogo wrote:Actually the paradigm to use inner (between modules) dependencies as the main mechanism to pull in a susbsystem, well separated from the rest,
is plain broken, in my opinion. Because dependecy tree cannot, in general, be robustly reversed for deinstallation (you are always in danger to pick up some external, in addition to internal dependencies).

Not on my two perfectly stable machines it's not.dmery wrote:Zork you are right, I totally agree with you. Gentoo now is a very "heavy" and unestable distro.
Regards,
dmery
Why not be more specific when you say something like that.dmery wrote:Zork you are right, I totally agree with you. Gentoo now is a very "heavy" and unestable distro.
Regards,
dmery
Heavy it may be, but thats what happens when you keep the source files on handdmery wrote:Zork you are right, I totally agree with you. Gentoo now is a very "heavy" and unestable distro.
Regards,
dmery

emerge -upv worldArturHawkwing wrote:I'm not a current gentoo user but I have to agree with a few (very few) of the things the original poster said. However I agree that creating posts like this is counter productive. I'm ussuming that the suggestion to create a "I HATE GENTOO" forum was just a jokeThe last time I tried gentoo was a few months ago. I kinda have the habbit of keeping a spare partition for installing differant distros periodically. Still like the one I'm using more though (for the record it's not Ubunto). Well anyways, doesn't emerge list what needs to be upgraded and the use flags it uses before anything is cast? I thought it did the last time I used it.
Well, the problem is that the critics are not exactly soft in their word choices either, there's more to constructive criticism than "it sucks and will ultimately die". I do agree that the original post, not regarding the title, does try to give advice instead of cursing.revertex wrote:It's sad to see what's happen with this community these days.
Some people point the gentoo weakness, and instead it be listened as a advise
that things need improvement ppl wish that he die horribly.
Sadly. But that's true for nearly anything under the sun, you will find windows users who say "Linux si teh suck", BSD users who say "Linux si teh suck", Debian users who say "Gentoo si teh suck", etc etc. As some people cannot stop to emphasize, Linux is about choice, so why not let everyone make their own choice?And even worse, they think that gentoo is only distro under the sun, all others sucks.
Well, I guess the gentoo XGL crew simply lacks a few people that would build releases stable enough to get into portage.Gentoo users need put their hands in some dirty to get bleeding edge things like XGL working.
N00bs can do the same in ubuntu without a CS master degree.
I do absolutely agree on this one. USE flags may be great in theory, but the way they're now, they create as many problems as they solve. One of the biggest problem with them is that if you're merging a package with, say, 50 dependencies, you'd better check about all the USE flags you do not know. While this might be okay, we lack the tools to do this efficiently. euse -i for each flag is not very efficient, and the descriptions do really suck. Take imlib, and that's not the worst example:What about dependencies?
Try do a frugal gentoo install with a *box as desktop, without kde or gnome,
then try install a package that depends on some gnome libs.
To install tsclient in a ubuntu bare install it have only a dozen dependencies,
less than 10mb of files to donwload.
Try install the same package in gentoo.
If you don't have gnome installed, it needs tons of packages, half gnome and a
huge download to accomplish, not to mention the time to compile these dependencies,
not to mention the bloat.
Sounds stupid to me, too much to get a small program like tsclient.
Why in hell almost all gnome packages depend on gnome-desktop and gnome-panel?
Do i need install this crap to use a gnome app in fluxbox?
USE flags seems a shot in the foot.
I think you're talking about kde for example, took quite long before 3.5 got stable, but I guess that problem finds its roots in the fact that gentoo is a sourcebased distro and the tree maintainers have to make sure it compiles cleanly against the other recent stuff. I can see that's more work than it is for a binary distro. Same goes for gcc4, I can perfectly understand why gentoo can not mark this stable as fast as other distros.What about the bleeding edge distro?
Or i should say "not so" bleeding edge distro or " a bit outdated" bleeding edge distro?
The only way to use up to date packages is unmask it an run a mix of a stable install
mixed with lots of unstable packages.
Agree on that one.People need to open their mind and eyes, not close their ears like we see in some posts here.
Gentoo really needs improvements, we see treads like these day after day not for nothing, its a advise.
Will absolutely NOT work if you want it to be stable. First, you lose the different CFLAGS, I don't think a communitydriven project can afford to have 9 repos just for the x86 subarchs. [Personally, I don't think that's a big problem. Imho archlinux is going the right way here with 586 repos.] Second, you will suffer USEflag breakage. If we cleaned up the USeflag-system, maybe. As it is right now, I don't think that would work.Why not a precompiled packages repository, it don't need to be a official gentoo
repository, but community driven.

Hrm. I'm not sure if I should take offense to this or not. I maintain Xgl for Gentoo (well at least 90% of Gentoo). If you ask the question "Can we maintain packages stable enough for portage?", the answer will always be "Doesn't matter. Gentoo won't allow Xgl in portage period, stable or not." because it hasn't been officially released and remains a branch of xorg-server. When it gets merged into the main branch (hopefully by the next xorg release) then it will be easy to have USE="xgl" enable it but for now, adding it as a separate package is (like Donnie Berkholz said) a complete hack. Ubuntu hacked it into their unstable release, well thats great but I guess you could say that Gentoo likes to do things "the right way" and not just hack stuff to make it work.dfy wrote:Well, I guess the gentoo XGL crew simply lacks a few people that would build releases stable enough to get into portage.revertex wrote: Gentoo users need put their hands in some dirty to get bleeding edge things like XGL working.
N00bs can do the same in ubuntu without a CS master degree.
Sorry, didn't mean to offend anyone. I'm not using Xgl at the moment, so that was rather a random guess. I hereby apologize.CoffeeBuzz wrote:Hrm. I'm not sure if I should take offense to this or not. I maintain Xgl for Gentoo (well at least 90% of Gentoo). If you ask the question "Can we maintain packages stable enough for portage?", the answer will always be "Doesn't matter. Gentoo won't allow Xgl in portage period, stable or not." because it hasn't been officially released and remains a branch of xorg-server. When it gets merged into the main branch (hopefully by the next xorg release) then it will be easy to have USE="xgl" enable it but for now, adding it as a separate package is (like Donnie Berkholz said) a complete hack. Ubuntu hacked it into their unstable release, well thats great but I guess you could say that Gentoo likes to do things "the right way" and not just hack stuff to make it work.dfy wrote:Well, I guess the gentoo XGL crew simply lacks a few people that would build releases stable enough to get into portage.revertex wrote: Gentoo users need put their hands in some dirty to get bleeding edge things like XGL working.
N00bs can do the same in ubuntu without a CS master degree.
By the way, if you think you can help make things more stable, I'm actively looking for help in this area (due to real life, I literally have no time to work on anything but ebuild maintenance).
see http://bugs.gentoo.org/show_bug.cgi?id=135329

Most of us are here because we're not satisfied with other distro's.revertex wrote:It's sad to see what's happen with this community these days.
Some people point the gentoo weakness, and instead it be listened as a advise
that things need improvement ppl wish that he die horribly.
And even worse, they think that gentoo is only distro under the sun, all others sucks.
Before criticize they at least should know a bit more about others distros.
As example, slackware has third part package managers that track dependencies
as portage do, you don't need to track dependencies.
CheckInstall does a great job if you need to install a package from source in a
slackware based or a debian based distro.
It automatically compile and make a .deb or tgz package with no trouble.
Slackware share the same simplicity of gentoo, you need to configure almost everything
by hand, but slack still working after you update some packages.
The wiki guide is perfectly coherent, if you can't follow it then you probably shouldn't be running such an unstable package as XGL. Ubuntu has it easier as they have prebuilt binaries, so their systems are roughly similar.Gentoo users need put their hands in some dirty to get bleeding edge things like XGL working.
N00bs can do the same in ubuntu without a CS master degree.
When you're building from source, you need various headers provided by other packages (e.g. Gnome). You also need need the libraries they provide (kdelibs anyone?), and the packages won't work without them. There are generally decent alternatives to all DE linked packages, you just need to do a bit more research.What about dependencies? Try do a frugal gentoo install with a *box as desktop, without kde or gnome,
then try install a package that depends on some gnome libs.
To install tsclient in a ubuntu bare install it have only a dozen dependencies,
less than 10mb of files to donwload.
Try install the same package in gentoo.
If you don't have gnome installed, it needs tons of packages, half gnome and a
huge download to accomplish, not to mention the time to compile these dependencies,
not to mention the bloat.
Sounds stupid to me, too much to get a small program like tsclient.
Why in hell almost all gnome packages depend on gnome-desktop and gnome-panel?
Do i need install this crap to use a gnome app in fluxbox?
The whole point of USE flags is to reduce bloat, by only enabling features that you need, rather than having a package that caters to everyone's needs. Put simply, its the Gentoo Way (tm), and it works for everyone else.USE flags seems a shot in the foot.
Looks like a bug.What about virtual packages?
I want to use thttpd, a very small thttpd server with awstats but awstats
need's apache, because the f8cking virtual.
What choice is Gentoo denying you? You can move the awstats ebuild to an overlay, and remove the dependency on Apache if you want, its likely just to break awstats.Isn't gentoo about the choices, to let the user decide what they want?
You can say what you want, but things like the uptake of GCC 4.1, modular Xorg, KDE 3.5 etc, show that Gentoo is still very much at the forefront of its niche.What about the bleeding edge distro?
Or i should say "not so" bleeding edge distro or " a bit outdated" bleeding edge distro?
Up to date packages are more unstable by definition, they have had less testing and may break things. The whole reason they're marked unstable is for your benifit, if you want to take the risks, run a ~arch system.The only way to use up to date packages is unmask it an run a mix of a stable install
mixed with lots of unstable packages.
Unfortunately that is an issue with Gentoo, but its a staffing issue. If you wanna help get more things stablised quicker, why not sign up as an arch tester?And why in hell some packages take ages to be marked a stable?
How many times you want install a package, but its marked a unstable,
or only work if you install a dependency marked as unstable?
I'd imagine gentoo64 is probably unstable, so it doesn't surprise me in the slightest you've had to unmask a load of packages to get it working. If you think thats a pain, try Gentoo FreeBSDYou know the rest, don't blame if you install unstable packages and it broke your system,
even if you are forced to install it to satisfy some dependencies.
Someone here tried gentoo64? its only usable if you unmask half of the packages.
Take a look at ubuntu, lots of packages marked as unstable in gentoo are in the current ubuntu repos.
And what about the worst nigthmare after dependency hell? the USE Flags hell?
Try USE flags per package, sounds really good, but in the pace that it changes,
and most part of time unnoticed, you will be in tigth pants soner or later.
Not to mention that my package.use has more than 100 packages.
Lots of things changed in these last years, and gentoo isn't the same distro that
claim to be fast, simple and that let the user have control over every aspect.
Why don't you post some constructive criticism then, instead of pointing out all the things that make Gentoo unique (Portage, USE flags, building from source) and saying they're wrong.I kown its not a distro aimed to n00bs, slackware and arch linux aren't too.
why maintain a gentoo install working getting even hard?
People need to open their mind and eyes, not close their ears like we see in some posts here.
Gentoo really needs improvements, we see treads like these day after day not for nothing, its a advise.
What would be the point of that in a source-based distro?Why not a precompiled packages repository
There are lots of unofficial package repositories, BMG and Sunrise being two examples.Lots of distro have unofficial packages repositories, look at Penguin Liberation Front as example.
It works very well, i can't see the point why gentoo haven't something like it, even after grow
with that huge user base like these days.
Its the perfect distro for us. If it doesn't suite you as well as Ubuntu, you're welcome to use Ubuntu, no-ones forcing you to use Gentoo.It seems that Gentoo is suffering the "Debian effect", a huge userbase, lots of packages avaliable,
a very outdated stable release, a comunity with a huge ego that thinks that its a perfect distro.
Do you even know what you are talking about !!! These baseless rant are annoying....revertex wrote:Someone here tried gentoo64? its only usable if you unmask half of the packages.
Short answer, yes.ikshaar wrote:Do you even know what you are talking about !!! These baseless rant are annoying....revertex wrote:Someone here tried gentoo64? its only usable if you unmask half of the packages.
I run a stable amd64 computer at work. Workstation settings with Gnome. I have ZERO unmask packages !! and only 8 packages keyworded ~amd64. None of these 8 are mandatory - the ONLY needed one for me was ncpfs for interaction with Novell server.
So let me return the question: Did you tried gentoo64 ??
PS: if your comment was based on test of amd64 from last year, well, welcome to a fast evolving distribution
I think s/he meant keyword rather than unmask and I do agree with that statement. To use AMD64 Gentoo on a desktop machine you DO have to keyword a LOT of packages (unless you don't like having anything installed). After a short time I had about 10, 15 things keyworded, at which point I just changed to ~ globally. So it's far from a baseless rant.ikshaar wrote:Do you even know what you are talking about !!! These baseless rant are annoying....revertex wrote:Someone here tried gentoo64? its only usable if you unmask half of the packages.
I run a stable amd64 computer at work. Workstation settings with Gnome. I have ZERO unmask packages !! and only 8 packages keyworded ~amd64. None of these 8 are mandatory - the ONLY needed one for me was ncpfs for interaction with Novell server.
So let me return the question: Did you tried gentoo64 ??
PS: if your comment was based on test of amd64 from last year, well, welcome to a fast evolving distribution
Hmm, that's strange as I've been running a amd64 box for some time and the only ~amd64 packages are ones that are usually unsupported stuff like gfxboot.Enverex wrote:I think s/he meant keyword rather than unmask and I do agree with that statement. To use AMD64 Gentoo on a desktop machine you DO have to keyword a LOT of packages (unless you don't like having anything installed). After a short time I had about 10, 15 things keyworded, at which point I just changed to ~ globally. So it's far from a baseless rant.