emerge: help place unified patch

[Patrick Spendrin]

Bernhard Reiter schrieb:
> On Tuesday 13 May 2008 23:26, Patrick Spendrin wrote:
>> Bernhard Reiter schrieb:
>>> On Thursday 08 May 2008 11:44, Bernhard Reiter wrote:
>>>> Having wasted some time with emerge again,
>>>> because of suprising "emerge --unmerge A B" behaviour
>>>> that will build and install B.
>>>> I have produced the following patch unify the current documentation
>>>> at one place.
>>> Shall I commit?
>>> (If there is no reaction for a week I would assume nobody cares
>>> and just commit, wouldn't I? :) )
>> Normally yes,
>> but in this very case I have two things against it:
>> 1) I am about to commit a brand new emerge.py which obsoletes those
>> changes as it uses OptParse from then on;
> 
> Very good! So when would "about" approximately be? :)
Well, I am waiting for reply of sysadmin@ to tag a first stable version 
of emerge then I will add the new stuff. There is one last thing to code 
(the environment variables that have been fixed in the other files 
already) then I will change the code hopefully soon.
> 
>> 2) I would like to have the information remain in the README as it is
>> kind of a spec against which I am developing.
> 
> I advise against using the README as spec and the duplication of 
> documentation. I suggest to use a TODO file (or TODO section in the README or 
> emerge.py) which keeps only the diff.
> 
> Wrong usage of emerge can lead to several hours of waited time which
> is frustrating, I can reassure you. :)
;-)
> 
> Bernhard
> 
> 
Patrick
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Kde-windows mailing list
> Kde-windows at kde.org
> https://mail.kde.org/mailman/listinfo/kde-windows


-- 
web:                 http://windows.kde.org
mailing list:        kde-windows at kde.org
irc:                 #kde-windows (irc.freenode.net)