[beports] Re: Development build (was Changeset 60)
- From: Schrijvers Luc <Begasus@xxxxxxxxx>
- To: beports@xxxxxxxxxxxxx
- Date: Sat, 24 May 2008 08:42:33 +0200
On vr, 2008-05-23 at 23:00 -0700, Jorge G. Mare (aka Koki) 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've been thinking ... there's also a file OptionalPackages in the
source where one could set the wanted third party stuff. Is this still
working? (try'd it yesterday without luck)
Second thing ... does the possix stuff all get installed when selecting
the Development package?
Wouldn't be the first that we need to compile (already included)
libraries just for the headers.
>
> 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?
>
One could argue that they are not directly needed, but I find Links
specialy interesting to fetch some libraries etc I want to compile
(although it still has some flaws). WB and VLC could be interesting for
those writing/porting translators/en- decoders).
> * 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.
>
Agreed.
> * 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.)
>
Atleast you have the skills for it. ;)
> 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
>
>
Luc
--
BePorts homepage - http://tools.assembla.com/BePorts
List archives: //www.freelists.org/archives/beports
Administrative contact: brecht@xxxxxxxxxxx
Other related posts:
