Re: E 0.9.3 release?

Mark Miller <[email protected]>
Newsgroups gmane.comp.lang.e.general
Message-ID <[email protected]>
 Hi Thomas,

In order to warm up the old release muscles, I tried building a new 0.9.3a
candidate on Windows <http://www.erights.org/download/0-9-3/>. (E does not
cross build. The binary for each platform must be built on that platform.)
For the first time, my Windows machine is now a Windows 7 machine. I ran
into a few problems. Since I upgraded directly from XP to 7, I do not know
if these new problems happened on the transition to Vista or to 7. A
different and more minor set of new problems seems to be caused instead by
upgrading my Cygwin.



Cygwin / C problems:

* New warning: "warning: array subscript has type `char'"
  for C code in byacc/j that seems innocent to me. And in any case is old
third party code.
* New warning: "file_utils.c:113: warning: `cygwin_conv_to_full_win32_path'
is deprecated
  which indeed it is because of the old unpleasant MAX_PATH restriction.
However, since this
  C code is used for very little I don't think we need to fix this for now.
IIUC, the restriction can
  cause at most a truncation rather than a buffer overflow.

Since we have been compiling our C code with "-Werror", those new warnings
were pointlessly causing our build to fail. I "fixed" it by suppressing the
"-Werror" in those two Makefiles.

I have committed the above minor changes to HEAD.


Windows Vista or 7 problems (i.e., since Windows XP):

I can build E fine on Windows 7. However, when I try to install it on
Windows 7, I get a bunch of (quite sensible) permissions violation errors
when I try to manipulate the registry. No annoying Windows 7 "do you really
mean it?" monologue boxes, just errors. However, when I install this same
binary on Windows XP, it works as well as it always did.


If anyone knows of a simple fix to get old cygwin/gcc C code for
manipulating the XP registry to work again on Windows 7, please let me know.

Assuming this doesn't work out easily, I'm inclined to pull all the registry
magic from the E installation. Would this inconvenience anyone? Does anyone
still care about, for example, the binding of the ".e" extension to the E
launching behavior?

Next up, reviewing your higher priority change lists, in order to create an
0.9.3b, which will be worth updating pages to state is the new official
release. I would like to stop using the download pages on erights.org and
instead use wiki.erights.org. Could I put the download files themselves
there as well?

Sorry this has all taken so long.


On Sun, Dec 19, 2010 at 11:38 AM, Thomas Leonard <[email protected]> wrote:

> On 9 November 2010 12:01, Thomas Leonard <tal-v5nx5w6akNyLE8xUarVfuPLx9OUvmyODWmv/[email protected]>
> wrote:
> > On Sat, 2010-11-06 at 20:11 -0700, Mark S. Miller wrote:
> >> On Sat, Nov 6, 2010 at 10:54 AM, Thomas Leonard <[email protected]>
> >> wrote:
> >>         The 0.9.2a release currently on the main web-site is rather
> >>         buggy. In
> >>         particular:
> >>
> >>         - it often fails to start (fixed in r718)
> >>         - it contains a known security flaw (fixed in r728)
> >>         - it suffers from various race conditions while running
> >>
> >>         Any chance of a 0.9.3 release?
> >>
> >>
> >> Yes, that's a good idea. I should be able to get to that in early
> >> December.
> >>
> >>
> >> Sorry I haven't been finding the time to review your outstanding
> >> changes. Could you maintain a page at wiki.erights.org pointing to
> >> outstanding changes, so that as I and others do find time to review
> >> these, we can easily find them? Thanks.
> >
> > Done: http://wiki.erights.org/wiki/User:ThomasLeonard
> >
> > I think the CapTP shutdown patches are the only ones that might be
> > useful in the next release.
> >
> > The Scope/EEnv split may be an API change, so it would make sense to get
> > a new stable release out first.
>
> Is there anything else needed for the next release? I snuck in a
> change to the caching of SQL statements, as a bit of profiling showed
> that most the time spent executing our SQL was actually converting the
> template to the new dlrHoles format! I'd be happy to leave the CapTP
> shutdown patches for the next version if that would speed up the
> release.
>
> Thanks,
>
>
> --
> Dr Thomas Leonard        http://0install.net/
> GPG: 9242 9807 C985 3C07 44A6  8B9A AE07 8280 59A5 3CC1
> GPG: DA98 25AE CAD0 8975 7CDA  BD8E 0713 3F96 CA74 D8BA
>
> _______________________________________________
> e-lang mailing list
> [email protected]
> http://www.eros-os.org/mailman/listinfo/e-lang
>



-- 
Text by me above is hereby placed in the public domain

    Cheers,
    --MarkM

_______________________________________________
e-lang mailing list
[email protected]
http://www.eros-os.org/mailman/listinfo/e-lang
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.