Development mailing list

Syndicate content
Archive of posts for haiku-development at FreeLists
Updated: 1 hour 28 min ago

[haiku-development] Non-standard headers in default compiler search path (Adrien Destugues)

Thu, 2015-04-23 19:45
Hi, I am working with the cdrecord developer to get it working on Haiku again. We found that /system/develop/headers/compatibility/bsd is in the compiler default include search path. This is a bit annoying, because the purpose of this folder is to hold non-standard functions we copied from the *BSD. This means the function names are not reserver and possibly a standard C application could redefine them (and use the same names for something completely different). ...
Categories: Development

[haiku-development] Re: The next release (Ithamar Adema)

Thu, 2015-04-23 19:45
On Tue, Apr 14, 2015 at 4:28 PM, Axel Dörfler axeld@xxxxxxxxxxxxxxxx wrote: releases and snapshot releases. Snapshots are taken at a point in time when code is more stableish. ...
Categories: Development

[haiku-development] Re: The next release (Axel Dörfler)

Thu, 2015-04-23 19:45
Am 14/04/2015 um 16:04 schrieb kallisti5: Any thoughts on going the Cyanogenmod route? Cyanogenmod has nightly releases and snapshot releases. Snapshots are taken at a point in time when code is more stableish. I think that sounds like a somewhat neat solution to our immediate lack of a release. ...
Categories: Development

[haiku-development] Re: The next release (kallisti5)

Thu, 2015-04-23 19:45
On 2015-04-14 08:52, kallisti5 wrote: On 2015-04-14 08:38, Adrien Destugues wrote: As for alpha / beta release repositories... Lets just set them to current by default and be done with it. ...
Categories: Development

[haiku-development] Re: The next release (Axel Dörfler)

Thu, 2015-04-23 19:45
Am 14/04/2015 um 15:25 schrieb kallisti5: I still don't understand what is so horribly known broken. (trac also confirms 0 blockers that are PM related). Our packages do need rebuilt and refreshed, but given you can install a nightly from a year ago and continuously update the same installation through today... that's pretty stable for nightly software :-) ...
Categories: Development

[haiku-development] Re: The next release (kallisti5)

Thu, 2015-04-23 19:45
On 2015-04-14 00:15, Adrien Destugues wrote: On Mon, Apr 13, 2015 at 08:42:04PM -0400, Andrew Hudson wrote: I also think we should now revisit whether the next release is Alpha or Beta. It's been quite a long time since our last serious release discussion, and since that time it is not clear to me that we have made any substantial progress towards resolving the package management issues. ...
Categories: Development

[haiku-development] Re: The next release (Axel Dörfler)

Thu, 2015-04-23 19:45
Am 14/04/2015 um 14:47 schrieb kallisti5: I already did this quite some time ago. We could add a warning that the last release is already quite outdated, and does not reflect the status quo. ...
Categories: Development

[haiku-development] Re: The next release (kallisti5)

Thu, 2015-04-23 19:45
On 2015-04-14 00:15, Adrien Destugues wrote: On Mon, Apr 13, 2015 at 08:42:04PM -0400, Andrew Hudson wrote: I also think we should now revisit whether the next release is Alpha or Beta. It's been quite a long time since our last serious release discussion, and since that time it is not clear to me that we have made any substantial progress towards resolving the package management issues. ...
Categories: Development

[haiku-development] Re: The next release (Adrien Destugues)

Thu, 2015-04-23 19:45
On Mon, Apr 13, 2015 at 08:42:04PM -0400, Andrew Hudson wrote: It's been quite a long time since our last serious release discussion, and since that time it is not clear to me that we have made any substantial progress towards resolving the package management issues. If we are stalled on package management, I think that will keep pushing a Beta release out, right?. So the next best option is Alpha 5 release. ...
Categories: Development

[haiku-development] Re: The next release (Andrew Hudson)

Thu, 2015-04-23 19:45
From: Earl Pottinger dmarc-noreply@xxxxxxxxxxxxx Subject: [haiku-development] Re: The next release noticed that when Haiku is mentioned on websites like OSNews and SlashDot.org that someone always claims the software has not been updated in years because the main Haiku-OS website points to Alpha-4 but there is no easy way for ...
Categories: Development

[haiku-development] Re: The next release (Earl Pottinger)

Thu, 2015-04-23 19:45
One very good reason to do a release whether it be Alpha or Beta is I have noticed that when Haiku is mentioned on websites like OSNews and SlashDot.org that someone always claims the software has not been updated in years because the main Haiku-OS website points to Alpha-4 but there is no easy way for beginners to see that the nightly updates from the same main page. Or at-least add a link to the nightly page on the main page below installing Haiku. ...
Categories: Development

[haiku-development] Re: The next release (Richie Nyhus-Smith)

Thu, 2015-04-23 19:45
Here is a list of requirements: 1) We need the thing to work and schedule build of packages on buildbots, Here is a list of nice-to-have things: ...
Categories: Development

[haiku-development] Re: The next release (Adrien Destugues)

Thu, 2015-04-23 19:45
13 avril 2015 16:40 Richie Nyhus-Smith richienyhus@xxxxxxxxx a écrit: case, I assign copyright for everything else. If I worked on Haiku sources under contrqct from someone else, they would get the copyright. I don't have stats on that but I think it is the same for most other devs. My point was that right now Haikungfu is as much part of the project as fRiSS ...
Categories: Development

[haiku-development] Re: The next release (kallisti5)

Thu, 2015-04-23 19:45
On 2015-04-13 09:40, Richie Nyhus-Smith wrote: Not all of the code in Haiku itself has copyright owned by Haiku, inc. In my case, I assign copyright to Haiku, Inc. for code I wrote under contract, but keep the copyright for everything else. If I worked on Haiku sources under contrqct from someone else, they would get the copyright. I don't have stats on that but I think it is the same for most other devs. ...
Categories: Development

[haiku-development] Re: The next release (Richie Nyhus-Smith)

Thu, 2015-04-23 19:45
but keep the copyright for everything else. If I worked on Haiku sources under contrqct from someone else, they would get the copyright. I don't have stats on that but I think it is the same for most other devs. My point was that right now Haikungfu is as much part of the project as fRiSS is. When I said 'changing the copyright', I meant changing the copyright that ...
Categories: Development

[haiku-development] Re: The next release (Adrien Destugues)

Thu, 2015-04-23 19:45
13 avril 2015 10:08 Richie Nyhus-Smith richienyhus@xxxxxxxxx a écrit: going to remain a 3rd assist Alexander What do you need to make it official? kallisti5 is a member of the ...
Categories: Development

[haiku-development] Re: The next release (Richie Nyhus-Smith)

Thu, 2015-04-23 19:45
What do you need to make it official? kallisti5 is a member of the Ownership of code written by a Haiku developer does not get automatically ...
Categories: Development

[haiku-development] Re: BBufferGroup questions for future work (Dario Casalinuovo)

Thu, 2015-04-23 19:45
Hello Jerome, thanks for help. I believe it's poor wording. There shouldn't be any duplicate ID in searching other buffer groups with the same buffer ID. This isn't a workaround. ...
Categories: Development

[haiku-development] Re: FreeBSD network drivers (Thomas Mueller)

Thu, 2015-04-23 19:45
until after our next release. The network drivers have been pretty stable lately, lets work on getting a release out first :-) -- Alex If two weeks after the release we are already telling people to use the nightlies because they have new network drivers, the release would be a failure. ...
Categories: Development

[haiku-development] Re: Gathering info on ownership of ARM dev boards. (Richie Nyhus-Smith)

Thu, 2015-04-23 19:45
Hi Ithamar, at the stage that we are at (and have been, for a _long_ time), I think a simple table of SoC vendors and their chips would be much more useful. Thing is, there's (less than?) a handful of developers that ever seriously work on the ARM port, and with the speed that it is progressing, whatever board is currently in use might be unsupported before we have user land properly booting on any board. We're pretty much at the start where the ...
Categories: Development