[FFmpeg-cvslog] r21226 - in trunk: Makefile common.mak subdir.mak

[Baptiste Coudurier]

On 1/24/10 7:17 PM, M?ns Rullg?rd wrote:
> Baptiste Coudurier<baptiste.coudurier at gmail.com>  writes:
>
>> On 1/15/10 11:26 AM, Reimar D?ffinger wrote:
>>> On Fri, Jan 15, 2010 at 08:16:28PM +0100, ramiro wrote:
>>>> Author: ramiro
>>>> Date: Fri Jan 15 20:16:28 2010
>>>> New Revision: 21226
>>>>
>>>> Log:
>>>> Get one step closer to world domination.
>>>> Remove "make uninstall".
>>>
>>> I'm all for a joke, but how about at least printing something
>>> useful in addition (if you really want after a sleep 1) like
>>> "Actually this way of uninstalling is just too unreliable, consider
>>> using a tool like (whatever Mans mentioned) and look in .... for
>>> files to manually remove").
>>
>> Well, I'm all for a joke as well. However I do use make uninstall and
>> I know why I'm using it. For example I want to remove the .a from a
>> static compilation because I want to test shared libs, or vice versa.
>
> That sounds like using the wrong tool for the job.  If you don't want
> static libs, use --disable-static.  I don't even see how uninstall
> could possibly be of relevance to what you seem to be describing.

I know how to compile with static or shared libraries. I use mainly 
static but sometimes I need shared for some applications, and sometimes 
I want to compile statically but shared libraries are taken in priority.

>> So far it has worked decently for me.
>
> One day your luck will run out.

We will see that day.

>> This removes the feature and I certainly don't want to rm the files
>> manually.
>
> You don't want is not a valid argument here.

It is a perfectly valid argument. I don't need another tool for this and 
certainly not a packaging system. There are systems that use none and 
has worked decently for years.

>> Printing the message is fine with me, but keep the uninstall working.
>> Thanks for your understanding.
>
> Keeping it working takes effort.  I will not waste my time on
> something that already has superior solutions.

For now it works. You are free to stop wasting your time on this, and 
_I_ will make sure it still works in the future. You are also free to 
step down as a maintainer.

You must at least ask people if removing this would affect their usage 
first, then discussing it. If you do not want to make sure it works, you 
must not forbid other people to do it.

There is no point discussing this, removing this feature is useless and 
will only annoy users and developers like myself.

-- 
Baptiste COUDURIER
Key fingerprint                 8D77134D20CC9220201FC5DB0AC9325C5C1ABAAA
FFmpeg maintainer                                  http://www.ffmpeg.org