[Bug 276614] graphics/mesa-dri:fix os_same_file_description warning

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276614

Ivan Rozhuk <rozhuk.im@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|Works As Intended           |FIXED

--- Comment #16 from Ivan Rozhuk <rozhuk.im@gmail.com> ---
(In reply to Gleb Popov from comment #15)

You are trying to marginalize me and what I do. It looks like this is your best
argument in defending your position.

1. I'm here because it is broken or absent.
This means that upstream or/and maintainer screwed up.

2. I solve my problems exclusively at my own expense. (with rare exceptions
when I do the paid work)
If you don't like it, you can hire me and then you can tell me what and how to
do.

3. I am not interested in the status, achievements, merits and everything else
with regard to the personality (mine or opponents).
I am here to solve a specific technical problem.

4. The whole system of ports is a set of crutches and hacks to allow software
to be written mainly for linux will compile and work for freebsd.
By calling my work a hack - you do not need to separate this from all other
ports.

5. Before saying that the results of my work I use only me - study the
question, 99% that you use the code written by me.



The whole story with GFileMonitor has been and still remains an example of how
much the gnome community does not care about the FreeBSD of users and how much
the FreeBSD community does not care about its own users.
This is a huge failure, for which all involved should be ashamed, but for which
no one was ever evened, and when they brought them a ready made decision in the
form of a patch, then the answer was: “Give us this in the form of a series of
single line changes” - this is just a spit in The face is personally to me, a
bureaucratic trick. And here this patch hung years before it was turned on.
I understand that for the gnome - FreeBSD is alien and they don’t care, but I
don’t understand why the FreeBSD community is so insolvent that the finished
patch cannot just accept for years.


> Just as I thought. This homegrown GFileMonitor backend isn't upstreamed and I'm 99% sure there are no users other than himself. I will remove this option once I find a time to convert libinotify-kqueue into a GFileMonitor backend.

6 or 7 years have passed already, and you have just gathered to do something!?
Here he is an example of complete failure.

libinotify-kqueue is a good solution, only it is late for 8 years.
Make sure your solution is not only easier to maintain but it also works better
before doing something.
Because it seems that it doesn’t matter for maintainers how it works, it is
important that it is easy to maintain.

-- 
You are receiving this mail because:
You are the assignee for the bug.