Proposal: new name: pbxbuild -> pearbuild
I recently I had an idea for a new name of the tool: pearbuild. I really like it and it would even preserve the namespace prefixes. What do you think? Hans ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: Proposal: new name: pbxbuild -> pearbuild
Hans, The only thing I'm wondering is why "pear" in particular? I think it's good, because it's imaginative. Additionally, I wouldn't have wanted the tool to be called gsxcodebuild or gspbxbuild or even gsbuild as I have a distinct allergy to things being prefixed with GS simply because they can be. Part of this comes from having committed the sin myself in the form of my "gopen" tool. :) The only reason it's not "open" is because there is an open keyword/tool on most versions of Linux with which it would conflict. O_o Also, it seems pbxbuild is the *previous* name of xcodebuild. So, it would be clearer when talking about pearbuild vs. pbxbuild vs. xcodebuild since it would be obvious you are referring to GNUstep's tool instead of a previous version of the build tool on OS X. GC On Wed, Nov 18, 2009 at 6:30 PM, Hans Baier wrote: > I recently I had an idea for a new name of the tool: > > pearbuild. > > I really like it and it would even preserve the namespace prefixes. > > What do you think? > > Hans > > > ___ > Gnustep-dev mailing list > Gnustep-dev@gnu.org > http://lists.gnu.org/mailman/listinfo/gnustep-dev > -- Gregory Casamento Open Logic Corporation, Principal Consultant ## GNUstep Chief Maintainer yahoo/skype: greg_casamento, aol: gjcasa (240)274-9630 (Cell), (301)362-9640 (Home) ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: Proposal: new name: pbxbuild -> pearbuild
A few more comments about pbxbuild since we're on the subject. I have a few suggestions regarding the code: 1) Separate out the code which does the actual conversion. It would be useful to have this as a library in case it could be used by other tools or apps, such as ProjectCenter. 2) Refactor the code which does the conversion. Currently it is somewhat procedural in nature. From looking at the structure of the xcodebuild file... it is a dependency tree. We can take one of two approaches with this: a) Make the tool do the building directly, such as with xcodebuild... this would mean that pbxbuild wouldn't just use make, but would become a full on make replacement b) OR find ways to make what is in the xcodebuild files into something equivalent in GNUstep-make files. Allow me to be clear here I am not suggesting in any way that pbxbuild become a replacement for gnustep-make or anything... only that pbxbuild would benefit from such enhancements. :) GC On Wed, Nov 18, 2009 at 7:49 PM, Gregory Casamento wrote: > Hans, > > The only thing I'm wondering is why "pear" in particular? I think > it's good, because it's imaginative. Additionally, I wouldn't have > wanted the tool to be called gsxcodebuild or gspbxbuild or even > gsbuild as I have a distinct allergy to things being prefixed with GS > simply because they can be. Part of this comes from having committed > the sin myself in the form of my "gopen" tool. :) The only reason > it's not "open" is because there is an open keyword/tool on most > versions of Linux with which it would conflict. O_o > > Also, it seems pbxbuild is the *previous* name of xcodebuild. So, it > would be clearer when talking about pearbuild vs. pbxbuild vs. > xcodebuild since it would be obvious you are referring to GNUstep's > tool instead of a previous version of the build tool on OS X. > > GC > > On Wed, Nov 18, 2009 at 6:30 PM, Hans Baier wrote: >> I recently I had an idea for a new name of the tool: >> >> pearbuild. >> >> I really like it and it would even preserve the namespace prefixes. >> >> What do you think? >> >> Hans >> >> >> ___ >> Gnustep-dev mailing list >> Gnustep-dev@gnu.org >> http://lists.gnu.org/mailman/listinfo/gnustep-dev >> > > > > -- > Gregory Casamento > Open Logic Corporation, Principal Consultant > ## GNUstep Chief Maintainer > yahoo/skype: greg_casamento, aol: gjcasa > (240)274-9630 (Cell), (301)362-9640 (Home) > -- Gregory Casamento Open Logic Corporation, Principal Consultant ## GNUstep Chief Maintainer yahoo/skype: greg_casamento, aol: gjcasa (240)274-9630 (Cell), (301)362-9640 (Home) ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: Proposal: new name: pbxbuild -> pearbuild
2009/11/19 Gregory Casamento : Hans, The only thing I'm wondering is why "pear" in particular? I think it's good, because it's imaginative. Additionally, I wouldn't have wanted the tool to be called gsxcodebuild or gspbxbuild or even gsbuild as I have a distinct allergy to things being prefixed with GS simply because they can be. Part of this comes from having committed the sin myself in the form of my "gopen" tool. :) The only reason it's not "open" is because there is an open keyword/tool on most versions of Linux with which it would conflict. O_o pearbuild because it builds apple software but in an non-apple environment, and there is a bit of impedance mismatch here. And because the prefix still would be PB. signature.asc Description: OpenPGP digital signature ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: Proposal: new name: pbxbuild -> pearbuild
ah! cool, then. :) On Wed, Nov 18, 2009 at 8:26 PM, wrote: > > > 2009/11/19 Gregory Casamento : >> >> Hans, >> >> The only thing I'm wondering is why "pear" in particular? I think >> it's good, because it's imaginative. Additionally, I wouldn't have >> wanted the tool to be called gsxcodebuild or gspbxbuild or even >> gsbuild as I have a distinct allergy to things being prefixed with GS >> simply because they can be. Part of this comes from having committed >> the sin myself in the form of my "gopen" tool. :) The only reason >> it's not "open" is because there is an open keyword/tool on most >> versions of Linux with which it would conflict. O_o > > pearbuild because it builds apple software but in an non-apple environment, > and there is a bit of impedance mismatch here. > And because the prefix still would be PB. -- Gregory Casamento Open Logic Corporation, Principal Consultant ## GNUstep Chief Maintainer yahoo/skype: greg_casamento, aol: gjcasa (240)274-9630 (Cell), (301)362-9640 (Home) ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: Proposal: new name: pbxbuild -> pearbuild
1) Separate out the code which does the actual conversion. It would be useful to have this as a library in case it could be used by other tools or apps, such as ProjectCenter. That would be appealing to me. I could envision an event-based API like for SAX, but I have to look at the code to see how that would work out. The other obviuos choice would be returning the object tree that already exists, while factoring out its traversing into separate classes. Probably the second approach will be more viable. 2) Refactor the code which does the conversion. Currently it is somewhat procedural in nature. From looking at the structure of the xcodebuild file... it is a dependency tree. We can take one of two approaches with this: a) Make the tool do the building directly, such as with xcodebuild... this would mean that pbxbuild wouldn't just use make, but would become a full on make replacement Surely this might be the greatest user experience, but may duplicate a lot of effort that already has been put into make. b) OR find ways to make what is in the xcodebuild files into something equivalent in GNUstep-make files. I tried to do that, there is some impedance mismatch though, because the xcode and GNUstep-make models differ somewhat. Hans signature.asc Description: OpenPGP digital signature ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: Proposal: new name: pbxbuild -> pearbuild
Am 19.11.2009 um 02:26 schrieb hansfba...@googlemail.com: 2009/11/19 Gregory Casamento : Hans, The only thing I'm wondering is why "pear" in particular? I think it's good, because it's imaginative. Additionally, I wouldn't have wanted the tool to be called gsxcodebuild or gspbxbuild or even gsbuild as I have a distinct allergy to things being prefixed with GS simply because they can be. Part of this comes from having committed the sin myself in the form of my "gopen" tool. :) The only reason it's not "open" is because there is an open keyword/tool on most versions of Linux with which it would conflict. O_o pearbuild because it builds apple software but in an non-apple environment, Some cultural background: in the german language we proverbial (don't) compare apples and pears (Äpfel und Birnen) as opposed to apples and oranges in english speaking countries: http://www.phrasen.com/uebersetze,Aepfel-mit-Birnen-vergleichen, 4592,d.html You can see this pun here: http://pearpc.sourceforge.net/ (PowerPC Architecture Emulator - basically a virtual machine which acts as a Mac), here: https://www.pearc.de/ (a company offering hackintoshes) and here: http://www.printmyshirt.co.uk/shop1.html?prodid=274 too. regards, Lars ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
