I've heard many times that squeak-dev is yet another fork of Squeak. It's NOT the case from my point of view because:
- squeak-dev is built on top of the last squeak release and beta versions - there is not a single patch applied in squeak-dev - it's only an aggregation of already existing packages that anyone can load in his base image
On Wed, Aug 15, 2007 at 11:29:42AM +0200, Damien Cassou wrote:
I've heard many times that squeak-dev is yet another fork of Squeak. It's NOT the case from my point of view because:
- squeak-dev is built on top of the last squeak release and beta versions
- there is not a single patch applied in squeak-dev
- it's only an aggregation of already existing packages that anyone
can load in his base image
I agree. it is a distribution, not a fork. Thanks for making it!
On Wed, 15 Aug 2007 02:29:42 -0700, Damien Cassou damien.cassou@gmail.com wrote:
I've heard many times that squeak-dev is yet another fork of Squeak. It's NOT the case from my point of view because:
- squeak-dev is built on top of the last squeak release and beta versions
- there is not a single patch applied in squeak-dev
- it's only an aggregation of already existing packages that anyone
can load in his base image
Agreed. I've been puzzled by this apparent misapplication of the word "fork", too.
Hi!
I've heard many times that squeak-dev is yet another fork of Squeak. It's NOT the case from my point of view because:
- squeak-dev is built on top of the last squeak release and beta versions
- there is not a single patch applied in squeak-dev
- it's only an aggregation of already existing packages that anyone
can load in his base image
I actually meant squeak.org when I wrote Squeak-dev. I was referring to the image maintained by the developers typically hanging on the squeak-dev mailinglist - and not your image which is called Squeak-Dev. Sorry for the bad choice of words. :)
So I haven't viewed your image as a fork, at least not yet. ;)
regards, Göran
2007/8/15, Göran Krampe goran@krampe.se:
I've heard many times that squeak-dev is yet another fork of Squeak. It's NOT the case from my point of view because:
- squeak-dev is built on top of the last squeak release and beta versions
- there is not a single patch applied in squeak-dev
- it's only an aggregation of already existing packages that anyone
can load in his base image
I actually meant squeak.org when I wrote Squeak-dev. I was referring to the image maintained by the developers typically hanging on the squeak-dev mailinglist - and not your image which is called Squeak-Dev. Sorry for the bad choice of words. :)
So I haven't viewed your image as a fork, at least not yet. ;)
Ok :-). But I heard it already that's why I wrote this mail. I hope things are clearer now.
Since its not a fork, and obviously not a spoon, and not mainstream, then what short term can be used to identify it?
Joking.. :)
On 15/08/07, Damien Cassou damien.cassou@gmail.com wrote:
2007/8/15, Göran Krampe goran@krampe.se:
I've heard many times that squeak-dev is yet another fork of Squeak. It's NOT the case from my point of view because:
- squeak-dev is built on top of the last squeak release and beta versions
- there is not a single patch applied in squeak-dev
- it's only an aggregation of already existing packages that anyone
can load in his base image
I actually meant squeak.org when I wrote Squeak-dev. I was referring to the image maintained by the developers typically hanging on the squeak-dev mailinglist - and not your image which is called Squeak-Dev. Sorry for the bad choice of words. :)
So I haven't viewed your image as a fork, at least not yet. ;)
Ok :-). But I heard it already that's why I wrote this mail. I hope things are clearer now.
-- Damien Cassou
2007/8/15, Igor Stasenko siguctua@gmail.com:
Since its not a fork, and obviously not a spoon, and not mainstream, then what short term can be used to identify it?
A distribution is perfect to me. Is really like a Linux distribution.
Joking.. :)
On 15/08/07, Damien Cassou damien.cassou@gmail.com wrote:
2007/8/15, Göran Krampe goran@krampe.se:
I've heard many times that squeak-dev is yet another fork of Squeak. It's NOT the case from my point of view because:
- squeak-dev is built on top of the last squeak release and beta versions
- there is not a single patch applied in squeak-dev
- it's only an aggregation of already existing packages that anyone
can load in his base image
I actually meant squeak.org when I wrote Squeak-dev. I was referring to the image maintained by the developers typically hanging on the squeak-dev mailinglist - and not your image which is called Squeak-Dev. Sorry for the bad choice of words. :)
So I haven't viewed your image as a fork, at least not yet. ;)
Ok :-). But I heard it already that's why I wrote this mail. I hope things are clearer now.
-- Damien Cassou
-- Best regards, Igor Stasenko AKA sig.
El 8/15/07 9:08 AM, "Igor Stasenko" siguctua@gmail.com escribió:
Since its not a fork, and obviously not a spoon, and not mainstream,
then what
short term can be used to identify it?
Joking.. :)
Maybe a knife ? Sure Damien image is putting some butter on bread ....
Edgar
"Damien Cassou" damien.cassou@gmail.com writes:
I've heard many times that squeak-dev is yet another fork of Squeak. It's NOT the case from my point of view because:
- squeak-dev is built on top of the last squeak release and beta versions
- there is not a single patch applied in squeak-dev
- it's only an aggregation of already existing packages that anyone
can load in his base image
Yet, you recently started requiring Monticello 1.5, which is a non-standard patch to a core part of the base system. How do you square these actions?
Lex
"Damien Cassou" damien.cassou@gmail.com writes:
I've heard many times that squeak-dev is yet another fork of Squeak. It's NOT the case from my point of view because:
- squeak-dev is built on top of the last squeak release and beta versions
- there is not a single patch applied in squeak-dev
- it's only an aggregation of already existing packages that anyone
can load in his base image
I did not realize you felt this way, but it is nice to hear. How do you square this view, though, with your recent inclusion of the Monticello 1.5 patches? These patches change the core image so much that their author says the word "patch" is not an adequate word to describe them.
I would think that, for a developer's universe compatible with 3.10, we need to also use the standard version of Monticello, whatever that version may end up being.
Lex
19 Aug 2007 12:16:57 -0400, Lex Spoon lex@lexspoon.org:
"Damien Cassou" damien.cassou@gmail.com writes:
I've heard many times that squeak-dev is yet another fork of Squeak. It's NOT the case from my point of view because:
- squeak-dev is built on top of the last squeak release and beta versions
- there is not a single patch applied in squeak-dev
- it's only an aggregation of already existing packages that anyone
can load in his base image
I did not realize you felt this way, but it is nice to hear. How do you square this view, though, with your recent inclusion of the Monticello 1.5 patches? These patches change the core image so much that their author says the word "patch" is not an adequate word to describe them.
I don't think including Monticello1.5 in future squeak-dev releases can be seen as a patch to Squeak. This is because, for me, Monticello is just a package. If an enhanced version, maintained by someone interested, is available, I would like people to start using it to discover bugs. However, Monticello1.5 currently has a bug which prevents me from releasing a new squeak-dev based on it.
"Damien Cassou" damien.cassou@gmail.com writes:
I don't think including Monticello1.5 in future squeak-dev releases can be seen as a patch to Squeak. This is because, for me, Monticello is just a package. If an enhanced version, maintained by someone interested, is available, I would like people to start using it to discover bugs. However, Monticello1.5 currently has a bug which prevents me from releasing a new squeak-dev based on it.
That's all fine, but you are still describing non-standard patches to the core image. Many people would call that a fork.
In my opinion, it would best to coordinate with the release team on this, at least as a place to start.
Lex
squeak-dev@lists.squeakfoundation.org