Re: today's git broke winetricks gecko :-(
There is one point in this discussion that I've been asking myself: Why does Wine need a Windows Gecko instead of a native (Unix/Linux) one? And if the question before makes any sense, wouldn't a native version be part of a firefox package and thus not need extra packaging? I'm sorry to ask such a simple question, but it's a long time that I've had any insight into the Wine details. Ciao Joerg -- Joerg Mayer We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology.
Re: DIB Engine : Almost 100% working
Hello (mostly wine package maintainers), On Sun, May 10, 2009 at 05:07:55PM +0200, Massimo Del Fedele wrote: > James McKenzie ha scritto: >> Good work. Have you started to think about how to get this into Wine >> where AJ will approve? > > Ah, I'm not very optimistic that it'll ever enter on wine tree :-) > Nor have I time to adopt the "trial and error" way up to it's > approved. > The easiest way I see by now is to add it to wine drivers as an > "alternative" driver in parallel to X11 one. > That could be done in less then 5 minutes and with no regressions :-) So from the end users point of view Alexandre is refusing this solution which is much better than what exists now into the official wine tree. To "solve" this problem from an end users view, I see two approaches: 1) Alexandre is willing to allow that code into the wine repository, so it can be maintained in sync with the existing wine code (it is my understanding that the modifications to existing code are quite small) and leave it to the user to choose which code to use. 2) We use the same solution that is used by the linux kernel developers: Keep the official source clean but add any (dearly wanted/needed) features as part of the distribution kernel. As I think that Alexandre has stated his preference (and I can understand him taking a long term view), I want to ask the packagers for the distros out there: Would it be OK for you to add the necessary patch into the code that you distribute. Personally, that means Marcus and the openSUSE wine packages :-) ciao Joerg -- Joerg Mayer We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology.
Re: [PATCH] fixed if check before strchr
On Tue, May 06, 2008 at 10:00:38PM +0200, Eric Pouech wrote: > > spath = strchr(spath, '\\'); > > -if (!spath) spath = strchr(spath, '/'); > > +if (spath) spath = strchr(spath, '/'); So the correct solution would be something like bpath=strchr(spath, '\\'); spath=strchr(spath, '/'); if (bpath && spath) spath=MIN(bpath, spath); else spath=MAX(bpath,spath); ? Btw, are Unix filenames that contain a '\' a problem? Ciao Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology.
Re: draft Call for Testing
On Mon, May 05, 2008 at 05:45:57PM -0700, Dan Kegel wrote: > 0. Make sure your machine runs glxgears properly > (if it crashes, you may need to update your graphics drivers) Why would I need working glxgears? Wine works fine for my every day work and I haven't had working 3D acceleration for the past few months. Ciao Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology.
Re: xfs getting case-insensitive filesystem support...
On Wed, Apr 23, 2008 at 08:39:40PM -0700, Dan Kegel wrote:
> Hrm. This is interesting:
> http://lwn.net/Articles/278961/
> I wonder if Wine could run faster if it could delegate
> the case-insensitvity to the filesystem...
Would be nice indeed, but I don't think it will come: Linus shot down
similar patches in the past because to_lower may be easy to implement
for ascii, but once you want to implement it for all charsets supported
by the files system it gets very messy.
Ciao
Joerg
--
Joerg Mayer <[EMAIL PROTECTED]>
We are stuck with technology when what we really want is just stuff that
works. Some say that should read Microsoft instead of technology.
Re: What happened to the videos from WineConf?
On Sun, Jan 06, 2008 at 02:47:24PM +0100, Maarten Lankhorst wrote: > and the big group photo OK, and now for those who were not there: An annotated version of that photo with a who is who pretty please :-) Ciao Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology.
Re: WineConf - Slides online
On Sun, Oct 07, 2007 at 01:41:10PM +0200, Marcus Meissner wrote: > I have uploaded the slides of Alexandres Status report > to http://wiki.winehq.org/WineConf2007 > > (direct link: > +http://wiki.winehq.org/WineConf2007?action=AttachFile&do=get&target=wineconf-20 +07-julliard.pdf > ) > > Feel free to upload more slides, and if you are lazy, send them to > me and I will ;) It looks like another presentation can be found at: http://stud4.tuwien.ac.at/~e0526822/wineconf_presentation.pdf.bz2 ciao Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology.
Re: WGL: Fix a major ATI regression
On Thu, Sep 13, 2007 at 01:09:14AM +0200, Roderick Colenbrander wrote: > The change isn't a hack but more a workaround. I have submitted the bugreport > to ATI but they likely won't fix it anytime soon. Well, if I understood the ATI development cycle correctly, even if they fixed it right away it will take another two releases (months) until it is released. ciao Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology.
Re: [PATCH 18/18] XCOPY: Add help
Umm, is there a specific reason why you created the mails by replying to the previous patch? This doesn't look that good with mailers that keep track of replies and e.g. indents them. ciao Joerg
Re: [meta-bug] I can not contact Jeremy Newman
On Mon, Aug 14, 2006 at 08:31:16PM -0500, Jeremy White wrote: > > It would be really helpful if you could add a constructive comment. > So, for example, if you could download and install the current > WineHQ version of Bugzilla and determine what settings mask > the emails, or work up a patch that accomplishes that, I'm sure > that Jeremy (or one of the other admins) would be happy to make > that change. And just to give you some hint I found in the wireshark bugzilla (no, we don't have that feature running either): http://www.bugzilla.org/features/#eam Our bugzilla manager didn't get it to work properly. So please find out how to and add it to the bug. Ciao Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology.
Re: has the LGPL licence fell through ? (forw)
as a simple reply isn't sent to the list - Forwarded message from Joerg Mayer <[EMAIL PROTECTED]> - Date: Wed, 21 Dec 2005 09:22:11 +0100 From: Joerg Mayer <[EMAIL PROTECTED]> To: Aric Cyr <[EMAIL PROTECTED]> Subject: Re: has the LGPL licence fell through ? In-Reply-To: <[EMAIL PROTECTED]> On Wed, Dec 21, 2005 at 07:48:09AM +, Aric Cyr wrote: > Maybe I'll fire off an email to Turbolinux to see what they have to say, > although technically unless I purchase or receive their product I am not > directly entitled to the GPL/LGPL code from them. Anyone have a copy of Can you please let me know why you think that? 2. You may modify your copy or copies of the Library or any portion of it, thus forming a work based on the Library, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions: a) The modified work must itself be a software library. b) You must cause the files modified to carry prominent notices stating that you changed the files and the date of any change. c) You must cause the whole of the work to be licensed at no charge to all third parties under the terms of this License. ... --- So I guess if they are using some code of yours that you provided to them under LGPL, you are entiteld to request the source. In case this goes to court you'll need a copy, but for now it is sufficient to be sure that they are distributing a product based on your code which is covered by the LGPL. Again: It is *you* who granted them the right to use your code, and by putting it under LGPL you made sure that you are entitled to any changes they make to *the* code once they start distributing your code (or derivatives) to thrid parties. That way you can reqeust the changes even when the new product costs $10M. Ciao Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. - End forwarded message - -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology.
Re: Stop-ship 0.9 problem
On Sun, Oct 02, 2005 at 08:19:58AM +0200, Lionel Ulmer wrote: > The only problem I see is with people having a self-compiled FreeType > library with hinting enabled. Why cripple their configuration too by default ? > > Is there no way to detect at compile / run-time what kind of FreeType > library we link with ? Or, at the very least, let this be configurable in > winecfg (or in the registry) as it does not seem to be the case with Mike's > patch. Full ACK! Ciao Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology.
Status of recent wined3d patches
Will the recent d3d patches by Oliver be committed? Thanks Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology.
Re: [QUARTZ] Add FFMpeg video wrapper filter
On Fri, Jun 10, 2005 at 12:19:06AM +0100, Christian Costa wrote: > This wrapper only support rle, msvideo1 and mjpeg for now. > To enable support for it, download lastest FFMpeg package, built it and > install it. > Also copy avcodec.h, rational.h and common.h into a ffmpeg directory > created in a > standard directory (/usr/include or /usr/local/include). > Once done, run configure to detect the library and the headers. > The library is static so there is no runtime dependency. I haven't looked at libffmpeg as a standalone library, but in case it's possible to do so, maybe runtime detection would be the way to go. That way wine binaries can be delivered without being patent challenged and video support can be added by just installing an additional dynamic lib. Ciao Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology.
Re: [HELP] Quartz and FFMpeg question
On Wed, Mar 09, 2005 at 06:33:44PM +0100, Christian Costa wrote: > > IIRC this third-party repository contains both the libavcodec package > > and the mplayer package so I suspect the two are very closely tied > > together. > > > > Yup. CVS repository are also hosted on the same site, the mplayer's one. > Building mplayer from CVS requires first to build FFMpeg from its CVS > repository too. The trick is to check out the ffmpeg cvs, move the libavcodec directory into the top level mplayer cvs directory and add the following line to mplayers top level CVS/Entries: D/libavcodec After that, libavcodec will be checked out automagically each time you do a cvs up in mplayer. Ciao Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology.
Re: Wineconf 2005
Hello All, would you consider having Wineconf 2005 during Linuxtag in Karlsruhe (Germany)? Linuxtag is from 22.-25. 06. 2005. I will ask the organizers of Linuxtag tomorrow whether they would be willing to provide infrasturccture during the event unless I hear a definitve no before. Going to Karlsruhe would be flying to Frankfurt or Stuttgart and then a single train to Karlsruhe. Ciao Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology.
Re: Directx9
On Tue, Sep 14, 2004 at 09:57:52AM +0100, Mike Hearn wrote: > I'm reminded of the saying, "if not now then when? if not you then who?" I think that once the API and the internal infrastructure are stable, the preconditions for that change are in place. > >Once Wine is declared to be ready for "ordinary users", the development > >process should indeed change. > > And when exactly is that? > > "Ready" is a mostly meaningless, arbitrary target. Many users are using > Wine today despite its official alpha-ness. When exactly: When Alexandre changes that line in the ANNOUNCE, so just guess who has the last word in this discussion :-) > >A good example on how to continue is KDE: > > KDE bears no resemblence to Wine, they have always done releases with > release management. I proposed to adapt the KDE release management to wine, once there is a "stable" branch. There are a lot of nice mechanisms that are worth evaluating. > There's no such thing for Wine. There is only increasing accuracy in the > emulation. The TODO lists that have been drawn up for 0.9 and 1.0 are > themselves pretty arbitrary: 0.9 has a theme of tidying up the > interfaces but still stuff like execshield support was in there, WM > rewrite and so on. Right, there *is* no such thing, but as written above, there *should be*, once Wine is officially declared ready for the general public > I don't think it makes any sense to put it off indefinately on the > grounds that Wine is still a developers-only release. That's circular logic. You are right on this point - there are some things to do: 1) decide when this sort of change/release will be done 2) how it will be done (Head/stable branch or some other model) 3) up to that point: don't slow down development by treating the wine tree like it was a stable branch. ciao Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology.
Re: Directx9
On Mon, Sep 13, 2004 at 01:55:19PM +0100, Mike Hearn wrote: > At *some* point we have to stop simply releasing CVS snapshots which may > or may not work/run important apps/eat your hard disk and actually do > proper releases that are, you know, tested'n'stuff. While this point will come eventually, it has not been reached: ANNOUNCE starts as follows: > This is release 20040813 of Wine, a free implementation of Windows on > Unix. This is still a developers only release. There are many bugs > and unimplemented features. Most applications still do not work > correctly. As long as it's "a developers only release", there is *absolutely no reason" why developers should not be allowed to break things for a while. Also, please consider how often Alexandre rejects patches not because they would not be an improvement, but because they should be improved even more. *That* would also have to change once you start talking about making releases that are truly intended for users. Honestly, I don't think that this time has come already - and from my point of view, this may remain for quite a while. Those users who feel differently currently have the option the use wine versions that have been developed/modified for user- use: Codewavers and Transgamings wine flavours. Once Wine is declared to be ready for "ordinary users", the development process should indeed change. A good example on how to continue is KDE: Currently, development is done in two different branches: HEAD and 3_3_BRANCH: In HEAD developers are free to develop things, add new things (and occasionally break things: HEAD doesn't even compile from time to time). 3_3_BRANCH must be stable, changes to it a reviewed etc. IMO, this would also be a good way for wine, once it's considered to be sufficiently stable and feature "complete". Ciao Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology.
Re: dsound mixer speedup
On Thu, Aug 12, 2004 at 12:24:20AM -0400, Robert Reif wrote: > Speed up mixing and unmixing by moving sample size and buffer > wrap tests to outside the loop. The code is not as compact or > pretty > but it should be faster. Just out of curiosity: *IS* it really faster? Maybe gcc already did the optimization? Ciao Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology.
Re: cards.dll
On Tue, Mar 16, 2004 at 12:09:24AM +0200, Shachar Shemesh wrote: > Can someone remind me again why we can't have GPL DLLs in the tree? > Doesn't the "call through documented interface blah blah blah not > derived work" argument cause the license for each two DLLs in Wine to be > independant? Basically it goes like this: LGPLed code can be run as a library, i.e. a function of an LGPLed dll can be called as a function call. GPLed code must be run as a (Unix) process if you want to use it from non-GPL-compatible code. See the GPL and especially the GPL FAQ for details. Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology.
Re: vsnprintf: glibc and win32 not compatible
On Mon, Mar 08, 2004 at 10:15:33AM -0800, Alexandre Julliard wrote: > Probably 3), but I don't think you want to start with the glibc code, > it's fairly ugly code, with many dependencies on glibc internals and > gcc-specific things. Hopefully we can find a more portable > implementation somewhere else. Ethereal brings its own version of (v)snprintf in form of the snprintf.[hc] files. While Ethereal is GPLed, the files in question are LGPLed. The files do not originate with Ethereal but I don't remember where they came from. Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology.
Re: Proposal: new mailing list wine-gov@winehq.org
On Mon, Feb 23, 2004 at 09:16:46PM -0800, Dan Kegel wrote: > We don't really have a procedure for starting new mailing lists. > Should we have a vote (a la the old Usenet group creation rules)? IMHO, it should just be created. It will not remove any traffic from the existing lists, so why should anyone care? It it turns out to be not used, it may still be closed down again. But that's for the experiment to decide :) Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology.
Re: Native NetBSD audio driver
On Mon, Feb 23, 2004 at 06:50:33PM -0500, Dimitrie O. Paun wrote: > I think quite the opposite is true: having an almost identical > driver in the tree simply obscures the matter more. The two will > diverge in time, and the NetBSD one will slowly bitrot. Now that > the two are the closest it's the time to document the differences > and integrate them in the OSS driver. I think that the future of Linux sound will be more with alsa than with oss. AFAIK, alsa does not exist with xxxBSD, so in my opinion, using and supporting the respective interfaces instead of oss makes more sense. Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology.
Re: MAPI
On Thu, Feb 19, 2004 at 11:27:02PM +0100, Enrico Weigelt wrote: > i've seen that mapi is currently not implemented. Well, I'd like > to sit down and code it, but I require several tools for that: AFAIK, the network format isn't documented anywhere. Ethereal is trying to dissect some of it, but there are lots of "This may be wrong.", "DISSECT_UNKNOWN" and "Unknown string.". In case you want to look at the network side of it: The code is in packet-dcerpc-mapi.c Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology.
Re: #winehackers IRC logs
On Sat, Feb 14, 2004 at 12:32:03PM +, Mike Hearn wrote: > On Fri, 13 Feb 2004 23:30:53 -0600, Jeremy White wrote: > > I have to confess that I'm mildly uncomfortable with this; I speak more > > freely in IRC that I do in email, at least in part because of the > > (admittedly foolish) notion that it's like speech - fleeting and > > ephmeral. > > Hmm. Yes, this is an interesting one. I wrote this stuff more to kill time > while I was feeling zoned than anything else, I can switch it off pretty > easily and wouldn't mind. Alternatively, would some way to selectively > disable logging help (log on/log off)? Although I haven't visited a wine channel for a fwe years now, I've always disliked the idea of having my speech (and typos) recorded. It's one thing to hold an online meeting with fixed starting end ending times and maybe even an agenda: Logging something like that makes sense. But when people are just thinking loud or "just" chatting - I think it's a win for everyone that things like that are *not* recorded (everyone includes the BigBrother fraction, although they don't realize this of course ;-) So if you feel that there are interesting things being said that are worth publishing, you should do it right: Record it, edit it manually and then post a summary. But, as I mentioned, I haven't been to one of the wine channels for a long time. Which reminds me... Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology.
Re: [Bug 1982] Can't SSH into a computer and use "wine cmd" or wineconsole
On Sat, Jan 31, 2004 at 01:24:49PM -0600, Wine Bugs wrote: > --- Additional Comments From [EMAIL PROTECTED] 2004-31-01 13:24 --- > I had already tried that. > > Connection to 192.168.0.1 closed. > (~)> ssh -X 192.168.0.1 > [EMAIL PROTECTED]'s password: > (~)> wine cmd > x11drv: Can't open display: Maybe a solution would be to ssh -x (in case -X is default)? Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology.
Re: File change notifications
On Thu, Jan 29, 2004 at 05:23:24PM -0800, Duane Clark wrote: > No, that is the named pipe problem. I retain a private patch in my tree, > which reverts the named pipe patch that causes the crawl. Just a thought: This is not the only time, where a hack is used to fix a specific problem/application that is unacceptable for inclusion into the source tree. How about adding a hacks/ directory where patches like this one can be collected and (more or less) maintained? The maintainance would be the responsibiblity of those who use the patch. Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology.
Re: Hack for the '-pthread' at make depend
On Sat, Jan 03, 2004 at 10:02:10AM -0800, Alexandre Julliard wrote: > "P. Christeas" <[EMAIL PROTECTED]> writes: > > > I thought of that when I was trying to see why the make had been broken. > > Unfortunately, the artsc-config script is not within "our" reach. Isn't the > > makedep utility supposed to have compiler's options as parameters? > > No, how could it? There's no way to know about all possible options > of all possible compilers. We should simply not use that broken config > script at all, and look for the header files ourselves. Wouldn't it make more sense to ask the authors of the artsc-config script to fix it? Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology.
