[beports] Re: Development build (was Changeset 60)

  • From: "scott mc" <scottmc2@xxxxxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx, beports@xxxxxxxxxxxxx
  • Date: Sat, 24 May 2008 06:48:53 +0000

crossposting this...
We were having a discussion over on the beports/haikuports list and it
turned to the dev images I was working on with sikosis, so I am moving
the discussion over to the dev list here.

On Sat, May 24, 2008 at 6:00 AM, Jorge G. Mare (aka Koki)
<koki@xxxxxxxxxxxxxx> wrote:
> Hi Scott,
>
> scott mc wrote:
>>>
>>> I am curious: what do the dev builds include?
>>>
>>
>> I just picked to install all optional packages, which includes:
>> development stuff
>> firefox
>> vision
>> vlc
>> wonderbrush
>> links
>> and pe
>> And whatever Ingo and company add in, I think I've seen some recent
>> additions like apr some others.
>> Be nice when we see subversion added into this ;)
>> I think everything else is in there to get right into developing though.
>>
>
> I have a couple of observations/questions, but I am not sure if this list is
> the appropriate one for this. If it is not, please tell me, and we can move
> it to the development list perhaps.
>
> * Being that this is a development build, does it make any sense to include
> apps like VLC, Links and WB?
>
> * Somewhat related to the above question (of what to include or not), I
> strongly feel that before we release the dev build into the cloud we need to
> give the core devs an opportunity to give their input on the content of
> these builds. I don't know if all the Haiku devs (or how many) are watching
> this list, but perhaps it is a good idea to post something on the
> development list before we take further action. Thoughts on this welcome.
>
> * Does the build have any readme file giving at least a brief description of
> what's included and perhaps pre-alpha disclaimers? If not, should we not
> include one? (I would be glad to try to write such a file if you guys give
> me some direction.)
>
> I apologize for what may come across as being picky. I really like the idea
> of releasing development nightly builds. But I do want to make sure that we
> do it right and (especially) with the endorsement of the core devs.
>
> Cheers,
>
> Koki
>
>
> --
> BePorts homepage - http://tools.assembla.com/BePorts
> List archives: //www.freelists.org/archives/beports
> Administrative contact: brecht@xxxxxxxxxxx
>

I'll set the AddOptionalHaikuImagePackages to: firefox, pe, vision,
and development if that sounds right for this (maybe links too?).  As
for a readme shoing up, i think that's possible as the OSSreadme shows
up now, just not sure what all it needs to say.
For now i'm making the images 1.8GB which seems to work out ok for my
porting work in vmware.  Using 7zip they sqeeze down to 53MD for
downloading.  Anyone else having opinions on what option to setup for
a developer's image?
-scottmc

--
BePorts homepage - http://tools.assembla.com/BePorts
List archives: //www.freelists.org/archives/beports
Administrative contact: brecht@xxxxxxxxxxx

Other related posts: