Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
DarwinPorts Packages (Mac OS X)
takeshimiya:
--- Quote from: afb on November 01, 2006, 11:09:32 am ---
--- Quote ---it's just that I see little point on it (no problem if you have time to mantain), because I either use a binary (dmg bundle), or I compile at hand CB.
--- End quote ---
Me too, but these are much easier to maintain (once setup).
In theory I can even have them run off a nightly cron job...
--- End quote ---
If it's not only theory, then :D
--- Quote from: afb on November 01, 2006, 11:09:32 am ---
--- Quote ---I see the point of having wxMac.mpkg because Darwin, err MacPorts is source-based, and compiling all the deps takes time.
--- End quote ---
The "mpkg" was because it held all those "pkg" inside of it.
So it was wxMac, and *every* little requirement for it too...
--- End quote ---
Understood, "all the deps takes time" is for that; I see the point in this case, and also there will not be much releases of this meta package as the dependencies will not change too often. :)
--- Quote from: afb on November 01, 2006, 11:09:32 am ---I still don't know why they are rushing wx 2.8 out, rather than have Apple use wx 2.7 for Leopard just like they used wx 2.5 for Tiger. But that's just me.
--- End quote ---
I think they want a stable-quality release (more or less),
"the pick-up date for Apple will be about Nov 13th, so that should be a
2.8 RC, counting back I'd welcome 10 days for bug fixing, so for me
Friday 3rd would be the latest day for spinning a 2.7.X, otherwise I
don't think I can have the quality we'd need
Thanks,
Stefan"
--- Quote from: afb on November 01, 2006, 11:09:32 am ---
--- Quote ----maintain officially the .cbp's in svn (Pecan?)
--- End quote ---
Haven't tried the offical .cbp, but I probably should.
--- End quote ---
Note that I'm talking about *_mac.cbp being included in svn
afb:
--- Quote from: takeshi miya link=topic=4345.msg34409#msg34409 ---Understood, "all the deps takes time" is for that; I see the point in this case, and also there will not be much releases of this meta package as the dependencies will not change too often. :)
--- End quote ---
This is why it is probably better of as a separate package, as it saves bandwidth and disk space. I think DP also does it as separate x86/ppc builds ?
For the "nightly build", it will bundle everything every time and do a universal build with both arches. It's the Apple way :-) (bandwidth and disk are cheap)
--- Quote ---I think they want a stable-quality release (more or less),
--- End quote ---
I guess renaming the Beta as "1.0" is better for marketing ?
It seems to have worked for Mac OS X 10.0, for instance... :-)
Well, whatever works for them... wx 2.7 and wx 2.8 are the
same API and generation anyway, so it's just a matter of names.
takeshimiya:
--- Quote from: afb on November 01, 2006, 11:36:16 am ---This is why it is probably better of as a separate package, as it saves bandwidth and disk space.
--- End quote ---
Yes, that's better in the packages case
--- Quote from: afb on November 01, 2006, 11:36:16 am ---I think DP also does it as separate x86/ppc builds ?
--- End quote ---
Please educate me, DP/MP is not only a source-based repository (as in gentoo) and Fink, a binary-based (as in debian binaries)?
I'm new to this
--- Quote from: afb on November 01, 2006, 11:36:16 am ---For the "nightly build", it will bundle everything every time and do a universal build with both arches. It's the Apple way :-) (bandwidth and disk are cheap)
--- End quote ---
Yes :lol:
--- Quote from: afb on November 01, 2006, 11:36:16 am ---I guess renaming the Beta as "1.0" is better for marketing ?
It seems to have worked for Mac OS X 10.0, for instance... :-)
Well, whatever works for them... wx 2.7 and wx 2.8 are the
same API and generation anyway, so it's just a matter of names.
--- End quote ---
Yes it's just a matter of names and it pays very important in marketing. 8)
Just look around this very forum and search for "we better wait for 2.8 stable releases" in the case of wx, or in the case of C::B itself look for "has development of C::B died?", "I'm using RC2".
These are examples that people, most of the time no matter what, looks first for the latest stable release, be it wx 2.8, CB RC2, Mac OS X 10.0, or any other piece of software.
afb:
--- Quote from: takeshi miya on November 01, 2006, 11:50:00 am ---
--- Quote from: afb on November 01, 2006, 11:36:16 am ---I think DP also does it as separate x86/ppc builds ?
--- End quote ---
Please educate me, DP/MP is not only a source-based repository (as in gentoo) and Fink, a binary-based (as in debian binaries)?
I'm new to this
--- End quote ---
It is, similar to Gentoo and FreeBSD Ports. I just meant that I don't think they support building "fat" binaries yet, but that you can only build for either architecture (x86 or ppc)
For the actual Portfile, I think the MacPorts reorganization seems to have killed most of the development... I got tired of waiting, so I set up my local build area instead. :-x
If and when they get their act together again, it might go into the main repository.
--- Quote ---
--- Quote from: afb on November 01, 2006, 11:36:16 am ---Well, whatever works for them... wx 2.7 and wx 2.8 are the
same API and generation anyway, so it's just a matter of names.
--- End quote ---
Yes it's just a matter of names and it pays very important in marketing.
--- End quote ---
But it doesn't matter on the technical level. Having an official
binary distribution of wxWidgets is much more useful to me
than having a "2.8.0" release - so I did a framework/package...
--- Quote ---Just look around this very forum and search for "we better wait for 2.8 stable releases" in the case of wx, or in the case of C::B itself look for "has development of C::B died?", "I'm using RC2".
These are examples that people, most of the time no matter what, looks first for the latest stable release, be it wx 2.8, CB RC2, or any other piece of software.
--- End quote ---
I am one of those. I like releases, whether alpha, beta or RC or final...
I think that Code::Blocks should release something some day soon.
afb:
The new codeblocks for wxGTK features a startup script,
that will start up X11.app and then launch Code::Blocks.
--- Code: ---/Applications/DarwinPorts/CodeBlocks.command
--- End code ---
This will make it more similar to the wxMac version...
(i.e. you have something to double-click to launch it)
Navigation
[0] Message Index
[*] Previous page
Go to full version