What number did Shane wish to tag on this developer release. I would like to update the freshmeat entries and also see if I cannot get Mike H's servers feel the heat of the /. effect .

Cliff

codepunk wrote

What number did Shane wish to tag on this developer release. I would like to update the freshmeat entries and also see if I cannot get Mike H's servers feel the heat of the /. effect .

Did you follow the HowTo? I want to be sure that the HowTos are totally correct before we do any updates to Freshmeat, Linuxberg, etc.

Wouldn't it be easier to create a snapshot as it is done for FPC?

Yesterday, I'll tried to build the win32 version to trace down the dependencies problem, but I ran
into some trouble when compling mwedit:
the units windows and classes declare both a type TPOINT. The classes type TPOINT hides that one of windows, so you get type mismatches if you call a windows function with this TPOINT. This applies to more type e.g. TRECT

I think the easiest solution �s to define TPOINT in classes only if the target isn't win32 else tpoint=windows.tpoint

Maybe another idea, to give one something clickable: I think I can manage to get a nightly build of lazarus, and upload this somewhere (together maybe with the used sources and binary compiler).

At least a lazarus binary would be nice, that's what the people want to see. the compiler is generated at 0:00 GMT, so if you're starting the download of a new compiler and rtl etc at 1:00 GMT it should be no problem.

> Maybe another idea, to give one something clickable: > I think I can manage to get a nightly build of lazarus, and upload this > somewhere (together maybe with the used sources and binary compiler).

If lazarus builds correctly i can add it in the daily script which is already run to build the current linux snapshots each day.

Peter

This is sort of what I meant by a release of Lazarus. We determine that it is at an interesting point in development and we package the source for everything in the Lazarus tree and combine it with the latest snapshot of the compiler (both Win32 and Linux). However I don't recommend that we attempt to do this every night. I would say we only do this over time when we have added new items that warrant interest or a version number change.

Another thing to remember is that there is already a .zip file of the lazarus source generated every night. We could just as easily create some URL links on the site to the nightly compiler snapshots and the nightly generated Lazarus source. If we created some easy to use scripts that are stored in CVS along with the source that works by downloading the source zip file and the compiler snapshot that would serve the exact same purpose.

+ From: Michael A. Hess
+
+ This is sort of what I meant by a release of Lazarus. We
+ determine that it is at an interesting point in development
+ and we package the source
+ for everything in the Lazarus tree and combine it with the latest
+ snapshot of the compiler (both Win32 and Linux). However I don't
+ recommend that we attempt to do this every night.

I don't mind to create a cronjob for a normal user which gets the CVS, compiles the compiler, if ok the compiles lazarus, if ok then put it in 3 archives (lazarus.bin.date.tgz, lazarus.src.date.tgz, fpc.bin.date.tgz)

This way you always have something that compiles.

+ I would say we only do this over time when we have added new items that
+ warrant interest or a version number change.

That would then be a symlink to a given archive.

+ Another thing to remember is that there is already a .zip file of the
+ lazarus source generated every night. We could just as easily create
+ some URL links on the site to the nightly compiler snapshots and the
+ nightly generated Lazarus source. If we created some easy to
+ use scripts that are stored in CVS along with the source that works by
+ downloading the source zip file and the compiler snapshot that would
+ serve the exact same purpose.

what I propose is to only create an archive if it compiles (and works), otherwise one will end up with somithing they can't try.

Marc

Florian Klaempfl wrote

Wouldn't it be easier to create a snapshot as it is done for FPC?

Well we can create a snapshot but what FPC snapshot do we base it on?

That is assuming it is a snapshot of compiled units. I don't think we can base it on a release version of FPC since bugs have been fixed to work with Lazarus. That means I will have to bundle a snapshot of the compiler along with the units.

Or we can just build a snapshot of the source that needs to go along with a snapshot of the compiler that they can download. However after we do all of that if they want to keep up with development they will have to use CVS, hence the need to make sure that the HowTos are correct. Which we are finding they are not.

Any opinions?

Should we create what we could call a release snapshot of the source?

If they want further updates they must use CVS until we do another release snapshot every few weeks?

What I am afraid of is that someone will try to use Lazarus with the wrong compiler (not the latest) and we will start to create a bad impression of the product both Lazarus AND FPC.

Michael A. Hess wrote

Any opinions? Should we create what we could call a release snapshot of the source?

I don't know. There are to many things changing to fast. Creating a source snapshot with a binary compiler makes most sense.
A binary snapshot won't work, because of the dependency problems a mentioned earlier, you will need the source to use the LCL units.

Maybe another idea, to give one something clickable: I think I can manage to get a nightly build of lazarus, and upload this somewhere (together maybe with the used sources and binary compiler).

Time by time we can decide what is a nice shot to show and if one wants the latest... they'll get it.

Marc

We should probably start a somewhat scheduled release. If the compiler is modified to work with lazarus that will go with the next release. Until a compiler patch is made that is done to fix something in lazarus we stick with the old one.

Right now until 1.0 these are only somewhat developer releases except for the fact that
the class libraries are almost fully usable. If mwEdit can run on lazarus LCL then just
about anything should be able to be built with it "mwEdit is one brutal piece of code".

Cliff Baeseman
------------------------------------------------------------------------ There is nothing wrong with Windows 2000 that LINUX won't fix!!! ------------------------------------------------------------------------

(snip)

what I propose is to only create an archive if it compiles (and works), otherwise one will end up with somithing they can't try.

IMHO this would be the best solution. We don't have to build anything manually and we'd also get to check if everything compiles nicely and, er, then ship it ;-)

/jarto