[openbeos] Re: unix software without tears
- From: "Mikael Jansson (mailing lists)" <lists@xxxxxxxxxxxxxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Sun, 02 Apr 2006 20:58:09 +0200 CEST
"Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx>:
>
> "Jonas Sundström" <jonas@xxxxxxxxxxx> wrote:
> > I think we could benefit from using NetBSD's 'pkgsrc'
> > for unix software management. (and unix software only)
> > It's unix-centric, of course, but it's far from NetBSD-only.
>
> I wouldn't consider it, if it's thought for unix software only; I
> would
> always only want one single update mechanism in the system.
>
> And what good would it bring?
>
> - we have all the tools that should be in the distribution in our
> source repository.
> - it's arguably a good thing to keep those up to date.
> - users should only care about updating those tools when there is a
> potentially
> security hole - all other updates should be managed by updating
> Haiku.
> - at least I don't see the need to have many other unix tools on
> Haiku,
> than
> those that are already part of Haiku.
>
... and, BeOS apps come in zip files, are unpacked in /boot/apps and
don't leave cruft behind!
Speaking of which, has a decision been done about where to store user
application data files, e.g. Quake maps? They're not binary add-ons, so
they don't go to the USER_ADDONS_DIRECTORY, nor are they settings. And
if you drop them in %A/data, they disappear when you upgrade the
application. Clearly, something like a B_USER_DATA_DIRECTORY is needed.
Opinions?
-- Mikael
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Building robots to do the mind-numbingly boring kind of work is the
fun kind of work, at least for a while. Once building robots becomes
boring, build robots that build robots." -- unknown
Other related posts:
