Does someone want to reign in this fuck-wit before she pisses of the whole community?
How can this be a dupe of a meta bug ?! The meta is supposed to regroup all such minor bugs. That's why it was created.
You say you want feedback, suggestions and bug reports yet this is what happens to constructive input.
Open source is about "if it does not do what you want , help fix it".
This comment indicates that once again she has not even read the fucking bug before dismissing it . May be you need to make ppl pass an english comprehension test before letting them edit bug reports.
Thanks fuck this nerd gets off on ranting on mailing lists, in real life she could do damage , well probably not actually, that's what it's all about.
Make of it what you like, I'm tired of pissing into the wind. See you all in 10 years time for 1.0
Best of luck to the majority who have put in all the hard work in creating a potencially excellent tool and dont think they're god's gift because of it.
I'm currently helping 5 first time user get used to Linux, my time will be better spent there.
Special thanks to Rob for the help he has given me.
On Sun, 25 Dec 2005 17:13:16 +0100, Wine Bugs wine-bugs@winehq.org wrote:
http://bugs.winehq.org/show_bug.cgi?id=4146
vitaliy@kievinfo.com changed:
What |Removed |Added
Status|UNCONFIRMED |RESOLVED Resolution| |DUPLICATE------- Additional Comments From vitaliy@kievinfo.com 2005-25-12 10:13
This is all belongs in the manual. There were numerous discussions about this on wine-devel. Wine is not Windows and we do not do things in windows ways. It's ap to packagers to create any link on the desktop or menu. And Wine should not associate itself with *.exe files - again up to packagers.
*** This bug has been marked as a duplicate of 75 ***
On Sun, Dec 25, 2005 at 09:47:39PM +0100, wino@piments.com wrote:
Does someone want to reign in this fuck-wit before she pisses of the whole community?
Well, tell this to Alexandre as he removed the '-h' stuff some time ago (we got more cases of people having problem with the 'wine foo.exe -- -a -b' syntax than with the '-h' problem).
As for the 'Start Menu', it's a packaging issue, not really a Wine issue per se.
And finally, why should we prevent people from running Wine as root ? I played the complete MI3 game as root (to have DGA support) and it worked just fine :-)
I still have problem with this whole discussion(s): people who do not know Linux should never use a command line window and should do everything from the start / run / foot / ... menu from their favourite distribution.
If someone starts Wine from the command line, I certainly expects him/her to be at least knowledgeable enough in how Linux works.
So effort should be spent on Desktop integration instead of futile stuff like adding '-h' help message or a 'running as root' protection.
Make of it what you like, I'm tired of pissing into the wind. See you all in 10 years time for 1.0
Yup, maybe by then we will see some patches too instead of just rants ?
Lionel
Le dimanche 25 décembre 2005 à 21:47 +0100, wino@piments.com a écrit :
Does someone want to reign in this fuck-wit before she pisses of the whole community?
How can this be a dupe of a meta bug ?! The meta is supposed to regroup all such minor bugs. That's why it was created.
I don't want to be part of your argument or to question the validity of the resolution your bug has been given; but the first thing I'd do is create separate bugs for separate problems. You should also give a more descriptive title to your bugs.
Examples:
1) "wine should not call wineprefixcreate when called without PROGRAM argument" 2) "wine -? and wine -h should be equivalent to wine --help" 3) "wine --help should tell user to check man wine" 4) "wine --help should link to winehq" 5) "wine installation should create links to winecfg in the windows'manager menu" etc.
Then you could create a usability meta bug (but meta bugs tend to be not very useful) and link these bugs with it.
This way if some of the bugs/enhancement are refused by the developpers you don't loose the chance to see some of your proposed changes to be implemented.
This is the same rational behind the fact that big patches that change a million things are rejected: some of your points/change may be valid, but your bug report/patch is useless because it asks/does things that are not accepted by the developpment team.
Last thing in http://bugs.winehq.org/show_bug.cgi?id=4146#c1, I don't know why you said sol.exe is a special case and I don't see why we should not tell user that he can use a valid unix path to run applications with Wine.
Please try to overcome your little trouble with Vitaliy and keep up with your efforts into helping Wine being more usable.
Happy Christmas everyone.
On 12/25/05, wino@piments.com wino@piments.com wrote:
Does someone want to reign in this fuck-wit before she pisses of the whole community?
Please calm the language down. If you can't be mature in a discussion, don't be a part of it at all.
You say you want feedback, suggestions and bug reports yet this is what happens to constructive input.
Marking a bug as a duplicate or anything else is not a put down. If that were the case, then hundreds of bug reporters should be offended, but they're not. Vitaliy reasonably gave his reasons for marking the bug a duplicate, and the original reporter, or anyone else, can change the bug if they see fit.
Concerning the original bug post, the other replies should satisfy your complaints about the outcome of this bug.
-- James Hawkins
wino@piments.com wrote:
------- Additional Comments From vitaliy@kievinfo.com 2005-25-12 10:13 ------- This is all belongs in the manual. There were numerous discussions about this on wine-devel. Wine is not Windows and we do not do things in windows ways. It's ap to packagers to create any link on the desktop or menu. And Wine should not associate itself with *.exe files - again up to packagers.
*** This bug has been marked as a duplicate of 75 ***
Those remarks are confusing to me, because winehq.org provides official binary packages. What's the correct place to report bugs with them if not the wine bugzilla? I don't see anything on the download page suggesting that the package maintainers should be contacted directly instead. That doesn't make much sense anyway, because it's a 'bug' with all of the packages. None of them provide menu entries or .exe file association AFAIK. (Admittedly I have only used the SuSE and Ubuntu/Debian packages in the last year).
Seeing as I was thinking of submitting some usability bugs that might be considered to be 'package' bugs myself, I'm interested on what the right thing to do is.
On 12/25/05, Joseph Garvin k04jg02@kzoo.edu wrote:
Those remarks are confusing to me, because winehq.org provides official binary packages. What's the correct place to report bugs with them if not the wine bugzilla? I don't see anything on the download page suggesting that the package maintainers should be contacted directly instead. That doesn't make much sense anyway, because it's a 'bug' with all of the packages. None of them provide menu entries or .exe file association AFAIK. (Admittedly I have only used the SuSE and Ubuntu/Debian packages in the last year).
You did the right thing by submitting the bugs to the data base, all he's saying is there are already bugs filed on this matter. And it's been discussed here on the development list and the bugs are known to the developers.
Seeing as I was thinking of submitting some usability bugs that might be considered to be 'package' bugs myself, I'm interested on what the right thing to do is.
Search the data base to make sure you don't file duplicate bug reports. If you don't find a report then file a new one.
Cheers,
Tom
-
James Hawkins -
Jonathan Ernst -
Joseph Garvin -
Lionel Ulmer -
Tom Wickline -
wino＠piments.com