Packaging Squeak for Debian and info on Stable Squeak

Göran Hultgren gohu at rocketmail.com
Wed May 23 09:42:17 UTC 2001


Hi Stephen and all!

--- Stephen Stafford <stephen at clothcat.demon.co.uk> wrote:
> On Tuesday 22 May 2001 10:36 pm, Simon Michael wrote:
> > Stephen Stafford <stephen at clothcat.demon.co.uk> writes:
> > > On Tuesday 22 May 2001  9:58 pm, you wrote:
> > > > O yes! :) Please go ahead, and let me know if you need debs
> > > > tested.
> > > >
> > > > You may have seen that "stable squeak", though not yet released,
> > > > has replaced the fonts. The new ones have some kind of special
> > > > license for squeak (which may or may be sufficient to get into
> > > > main).
> > >
> > > oh?  Do you have a URL for this new license?  (I would prefer to
> > > get it into main if I can)
> >
> > No. Check out the stable squeak article announced on the list
> > recently; the stable squeak folk should be able to tell you more.

I have included the licenses there now, see at the bottom of the article:

http://195.43.243.112:8000/sqworld.1

For details regarding whether the note added to SqueakL has been approved by Apple etc, drop an
email to the alias stsq at bluefish and you will reach the core team working on Stable Squeak,
because I have no idea! And other questions about SqueakL not being appropriate for Debian main
etc. I have no idea about either.

> > Also, there are some existing squeak debs as Bert pointed out - I
> > can't recall who that maintainer is. It may be worth thinking about
> > how multiple squeak versions should co-exist (released squeak &
> > testpilot squeak from SqC, the stable squeak fork, etc.) Also how
> > often to update the package(s) ? Perhaps:
> 
> Hmm, most likely they would have to be packaged seperately and conflict 
> with each other.

Well... perhaps I am missing something, but why do they need to conflict?

[SNIP]
> > - a separate stable-squeak package is made available when that shows
> > up. I imagine there will be a need for separate packages for a while.
> 
> indeed...depending on how much is different it might be possible to 
> distribute stable-squeak as a patch to squeak proper.  Or perhaps not.  
> I will look into it once I have the initial package uploaded and 
> installed.

Stable Squeak will initially be very different. It is definitely not a patch.

Andreas Kuckartz wrote:

> If you like to promote Squeak by adding it to a Linux distribution please do
> not wait for the thing named "Stable Squeak". What counts here is that it is
> an Unreleased Squeak.

My guess is that Stable Squeak will be released very soon. I have builds dropping in my inbox
almost every day (literally) from Paul. Paul and Joseph are in the middle of getting the source
management tools bugfree and chopping up the current image into true modules.

The idea is that until this is done a release might just cause more problems - and there is a
point. IMHO I think Stable Squeak should open up NOW . I do not think anyone involved has anything
against opening up, it is just that they really want this crucial part with the source management
to work before we all throw ourself into it. And I also think there are other issues that should
be discussed and perhaps planned before a release, se the forkingscenarios below.

About packaging for Debian:

There is no point in waiting to pack Squeak until Stable Squeak is out for 2 reasons. The first
reason is that Stable Squeak is not released yet. The second reason is that when it will be
released it will be quite a different beast than regular Squeak. It will be a fork based on Squeak
2.8 with a lot of new and different code. So we will have two distinct different Squeaks for some
time.

Exactly what will happen then is... interesting. I have no idea and I think that the Stable Squeak
team really wants a lot of help from the community to figure this out. Will there be two different
flavours of Squeak living side by side? What will SqC do? Will the two update streams managed by
Disney (currently 3.0 and 3.1a) continue to be directed at regular Squeak? If so - which sounds
like most probably - who will manage Stable Squeak and how? How will for example Morphic evolve in
Stable Squeak? Will regular Squeak become something similar to Debian unstable/testing and will
Stable Squeak pick things up from there? Will that work even though regular Squeak does not adopt
the new source management framework in Stable Squeak? etc. etc. etc... :-)

As I have only ideas and questions and no really good answers I will stop here. ;-)

regards, Göran


=====
Göran Hultgren, goran.hultgren at bluefish.se
icq#:6136722, GSM: +46 70 3933950, http://www.bluefish.se
"Department of Redundancy department." -- ThinkGeek

__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/





More information about the Squeak-dev mailing list