2/28/2024 0 Comments For mac instal Unite![]() I'm also looking into deploying a forum software of some sort so people can direct questions at the builders about building in general, errors in their own build attempts, those sorts of things. That's user confusion in a bottle right there. Options aren't bad, we just don't need a handful of guys compiling with nearly identical configs and posting builds. If there are good reasons for maintaining alternate builds for the same CPU, we'll maintain them. On the opposite end of focus is choice, and that's also something we want to promote. For instance, I and drumstrick are both building G5 builds at the moment, but he's done much more research into G5 optimization flags for the compiler than I, so if we get going, I'll gladly discontinue my G5 build in the interest of lessening confusion and focusing my work toward need. That's not to say I'm not for merging some redundant building together into one person's charge. So for each type of build from each builder there would be a separate, trackable site listing and rss feed, so that once a user settles on a builder they prefer, it's easy for them to track that builder's progress. These would replace the cpu designations in the feeds and the web page. My idea for adapting this to multiple builders is to make build type more of a build identifier rather than a cpu type, so that way I'll have a section for something like elfurbe-g3-trunk and (hopefully) ozjason-g4-trunk or drumstick-G5-release. As many as I have on the server for that cpu type will be in each list. ![]() It will always be four items long, but will always be the four newest builds, one from each cpu type, at least while it represents only my buildsĮach of these feeds will show all the currently "available for download" builds for each cpu. This feed shows just the newest build from each build type. I've also got dynamic rss feeds going, which seems pretty choice. That means that we won't be reliant on an editor or someone actively updating the pages, meaning that us builders can just be builders most of the time, and just upload our builds as they complete, and everything else works its way out. While ugly at the moment, the important thing to realize is that the page updates automatically when I post new builds. I've already started building the framework for this site as my own distribution site. ![]() I proposed that we create a unified web site where we can gather all our builds together and offer them to the curious Mac tweaker with explanations about what's different between builds, how to identify your processor type, how to build for yourself if you feel studly, those sorts of things. ![]() I have no time for keeping all those things updated, and so the idea popped up to organize the current trunk and release builders for MacOSX into a Firefox Mac Community Build Team. However, powerbook was also compiling release builds with optimization as well as keeping track of bugs and tutoring poor lugs like me who just want the fastest Fox they can get. I, however, as a fan of his builds, decided to take up some of his gauntlet and continue building speed-optimized firefox builds from the Trunk. As many probably know, powerbook, a long time firefox builder for MacOSX has decided to switch to Camino, mostly stemming from consistently ignored bugs and seeming indifference from moz.org about making the Mac version as good as it's PC counterparts.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |