On 16/02/2015 17:06, Donn Cave wrote:
Quoth =?windows-1252?Q?Axel_D=F6rfler?= axeld@xxxxxxxxxxxxxxxx,
...
From the POV of the implementors of PM, there was no reason to keep the
old paths intact, as *nothing* should have used fixed paths in BeOS --
I've read this a few times, but have no idea what you're talking about.
What is the implied alternative to fixed paths?
Something like
...

Quoth =?windows-1252?Q?Axel_D=F6rfler?= axeld@xxxxxxxxxxxxxxxx,
...
From the POV of the implementors of PM, there was no reason to keep the
old paths intact, as *nothing* should have used fixed paths in BeOS --
I've read this a few times, but have no idea what you're talking about.
What is the implied alternative to fixed paths?
I don't have any applications out there to speak of, but I started with
BeOS when it only ran on the BeBox, have the Be Developer's Guide, was
...

Am 15.02.2015 um 19:06 schrieb Jim Saxton:
The proper way to accomplish this would have been to leve the
directory system as it was under the home directory but add a
Packaged directory tree. ~/config/Packaged. This way anything in the
packaged directory would be read-only, and anything in the normal
directory tree would stay read/write. This way, an app that drops libs
in say ~/config/lib would still work without needing to be packaged.
...

On 02/16/2015 01:51 AM, Sean wrote:
haiku rocks, do not reply
Please refrain from sending test mails to mailing lists. You're
violating netiquette for no useful purpose. If you have nothing to say,
there's no point in testing whether your mail would reach the list,
anyway. Otherwise you can just send whatever meaningful contribution you
...

On Sun, Feb 15, 2015 at 10:06:09AM -0800, Jim Saxton wrote:
The proper way to accomplish this would have been to leve the
directory system as it was under the home directory but add a
Packaged directory tree. ~/config/Packaged. This way anything in the
packaged directory would be read-only, and anything in the normal
directory tree would stay read/write. This way, an app that drops libs
in say ~/config/lib would still work without needing to be packaged.
This would have had nothing to do with how PM works, only with the
...

The original plan was a bit different, the idea was to let users write
to non-packaged and get these changes visible in the packaged view of
the system. This was dropped because there was an unreasonable
performance hit in doing this, and it didn't really break any
well-behaving BeOS app. Yes, it does means some changes to the FS
hieararchy, but this was already changed from BeOS several times in the
past (booting a BeOS install is enough to notice that).
So, the completely separate non-packaged directory hierarchy is a
tradeoff: a slightly more complex FS hierarchy, but a system which works
...

Quoth Michael Crawford mdcrawford@xxxxxxxxx,
...
So strictly speaking I would be creating a fork.
I think you could have left strictly speaking out - you sure will
be creating a fork, off a system that's a long ways from even beta.
I'm still curious where your application software is coming from, to
make a user platform that you can ask money for. Do you actually
have this running? I want to get me some of that! I'm thinking of
...

On Sat, Feb 14, 2015 at 05:21:32PM -0800, Jim Saxton wrote:
On 2/14/15, Matthias Lindner two4god@xxxxxxxxx wrote:
Hi Jim Saxton
if you followed the haiku website closely there where a lot information
before it was implemented,
the first discussions on the mailing list even dates back to 2001:
it always showed up from time to time at the malinglist, on irc and so on.
...

On Sat, Feb 14, 2015 at 10:18 PM, Michael Crawford mdcrawford@xxxxxxxxx
wrote:
What I would do is to explore the nightlies for the most-stable
version of each software package.
None of the software in HaikuDepot has gone backwards in terms of stability
(AFAIK), only the system itself has. And even then it's usually fixed
quickly.
...

On 15 February 2015 at 03:12, Michael Crawford mdcrawford@xxxxxxxxx wrote:
I would give it a
distinctive trademark that made clear that while derived from Haiku,
it was not your product, I don't know but something like Mike's
Haiku.
I don't think you could use Haiku in its name, check with Haiku Inc. [1].
In any case, I hope you'll prominently state, that you've forked an
alpha (or in some time beta) version of Haiku and explain to your
users that this means unfinished/unstable.
...

On 15/02/2015 4:19 PM, Michael Crawford mdcrawford@xxxxxxxxx wrote:
What I would do is to explore the nightlies for the most-stable
version of each software package.
There are some packages that have formal test scripts or written test
plans. To the extent that they do, I'd run them, then provide the
specific version of the package that passes the most tests.
I expect that I would omit packages that I regard as unstable, or that
...

What I would do is to explore the nightlies for the most-stable
version of each software package.
There are some packages that have formal test scripts or written test
plans. To the extent that they do, I'd run them, then provide the
specific version of the package that passes the most tests.
I expect that I would omit packages that I regard as unstable, or that
are at a very early stage of development.
...

Quoth Michael Crawford mdcrawford@xxxxxxxxx,
... One way I have in mind is to sell a supported version of Haiku.
Have you been using Haiku much? What version of Haiku would you sell?
- the latest alpha release, R1A1? Which is significantly out of date.
- some nightly release to be decided later?
- the next official alpha or beta release?
- the first supported release?
...

Hello,
IIRC one of the main reasons Haiku was released on MIT License was
that if any company wanted to take the source and develop their own
version of the system, they would be free to do so without bothering
themselves with licensing issues. Even if they closed the source,
Haiku would still be there, and appearance of the commercial version
of the system would benefit whole ecosystem.
Having that in mind, I think as long as you comply with the trademark
...

Friends,
I was one of the more active Be developers - #6922 - but have been
only marginally active in the Haiku community. I keep intending to
contribute, but then life keeps intervening.
I'd like to find a way to do well by doing good. One way I have in
mind is to sell a supported version of Haiku. I would give it a
distinctive trademark that made clear that while derived from Haiku,
it was not your product, I don't know but something like Mike's
...

On 2/14/15, Matthias Lindner two4god@xxxxxxxxx wrote:
Hi Jim Saxton
if you followed the haiku website closely there where a lot information
before it was implemented,
the first discussions on the mailing list even dates back to 2001:
it always showed up from time to time at the malinglist, on irc and so on.
...

In short, are bundles really a good means of packaging *all* software? If
not, is it really such a problem having to install a bundle. Installation
could be reduced to just extracting the bundle.
I feel that this is where package management went off the rails. The idea of
extracting the package was never seriously considered which led to adding
special read only directories to house the packages and all the consequences
that go with that.
...