On Sun, 6 Feb 2011 12:53:20 +0100, Cedric Sodhi wrote:

> > > 1. With a sudden change portage would simply resync to a new
> > > directory, the old tree would rot in /usr  
> > 
> > And people would hit problems because /var bas filled up! I'm not
> > saying the current default is right, it's not, but you are
> > over-simplifying the work involved in making a change.  
> 
> I disagree. You are overcomplifying it instead. The proposed patch would
> involve exactly:
> 
> 1.) Change the default (the value that is used if no explicit value is
> given)
> 
> 2.) etc-update make.conf to explicitly specify the old location as the
> desired value.
> 
> Period.

So now you've added another step not previously mentioned, but one that
just happens to answer the point I made? Your previous 1 statement is
now no longer true, portage would not resync to a new directory, and the
old one in /usr would continue to be used, only new installs would be
affected.


> Your attempts to argue that patching portage with that simple change
> would introduce problems of unpreceeded magnitude are pharisaic. It's
> the same though significantly simpler as other updates to whatever
> package you like.
> 
> Your argument that the developers should not be bothered with minor
> issues such as this one because they have bigger issues is the
> trillionth logical fallacy in this thread.

My argument? Please quote my statement to that effect?

> I'm honestly tired of it and
> I will not counter argue this because the wrongness of your reasoning
> should be trivial to spot with at least a minimum of thought.

I mentioned one drawback to your previous proposal, that you now claim is
wrong only because you changed your proposal to contradict your
previous post. Your powers of extrapolation far outweigh mine and I give
way to your superior "reasoning".
  
> > Actually, the way to make the change is not to change the default,
> > yet, but to change the default make.conf for new installs, and the
> > accompanying documentation. That way existing systems are unaffected,
> > which is how it should be with a change of default.  
> 

I see you chose to not comment on this, even though you quoted it? 

Did it not fit in with your trolling?

Attachment: signature.asc
Description: PGP signature

Reply via email to