We'd *love* to have you back in action Ted! Even just a bit of code here or there would go a long way :)
G ________________________________________ From: Ted Bullock [tbull...@comlore.com] Sent: Tuesday, September 27, 2011 5:53 AM To: Garrett Serack Cc: Adam Baxter; madewokh...@gmail.com; coapp-developers@lists.launchpad.net Subject: Re: [Coapp-developers] I think we'll want to fork gnulib Boy, I keep looking in on this project and thinking I need to make time (somehow?) in my schedule to commit. Sheesh, Anyway, fork it and fix it is the right answer. On Mon, Sep 26, 2011 at 6:40 PM, Garrett Serack <garre...@microsoft.com> wrote: > I would agree. I'd *rather* not go down the route of making > a compatibility layer for stuff, the better approach is to fix the code to > do what's right on Windows, and deal with what comes back. > Now, that being said, there are going to be times when we'll need to make a > (thin-as-possible) layer to achieve our goals. > G > ________________________________ > From: coapp-developers-bounces+garretts=microsoft....@lists.launchpad.net > [coapp-developers-bounces+garretts=microsoft....@lists.launchpad.net] on > behalf of Adam Baxter [volta...@voltagex.org] > Sent: Monday, September 26, 2011 5:35 AM > To: madewokh...@gmail.com > Cc: coapp-developers@lists.launchpad.net > Subject: Re: [Coapp-developers] I think we'll want to fork gnulib > >> I think that depends on how far we're willing to go to avoid modifications >> to the original source. >> >> If we tried to provide grep with the failure code it expects, I think >> >> that would bring us into compatibility layer territory. Instead, we >> >> should just accept that that's how windows works and modify grep to >> >> account for it. > > Sounds reasonable, but probably best to defer to Garrett and other people > who know more than me - do we focus on shallow forking the libraries, the > applications or take it on a case by case basis? How should the CoApp > project deal with the concepts of making the software work within the > Windows ecosystem, rather than going down the Cygwin route of bringing > Unixisms to Windows? (maybe that discussion belongs in a new thread?) > > --Sfsm > > > > _______________________________________________ > Mailing list: https://launchpad.net/~coapp-developers > Post to : coapp-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~coapp-developers > More help : https://help.launchpad.net/ListHelp > > -- Ted Bullock <tbull...@comlore.com> _______________________________________________ Mailing list: https://launchpad.net/~coapp-developers Post to : coapp-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~coapp-developers More help : https://help.launchpad.net/ListHelp
