You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Michael Sweet <mi...@easysw.com> on 2004/04/19 18:52:23 UTC

Bugs/comments on 1.0.1

All,

I'm in the process of playing with subversion for the first time,
and have run into some issues:

     1. There is no easy way to disable the Apache module via the
        configure script; what finally worked is:

            ./configure --without-apache --without-apxs --without-neon
                --disable-mod-activation

        I'm not sure if "--disable-mod-activation" is necessary, but
        it would be nice to have a global "--disable-apache" option
        to build without the Apache stuff.

     2. "make install" will not work on a system without makeinfo
        on it.

     3. DB 4.0.x does not appear to work with the current Subversion;
        I got a "function not implemented" error when creating a new
        repository...  After upgrading our installed DB library to
        4.2.52 everything seemed to work OK.  It might be worthwhile
        to document that 4.0.x may not work at all...

-- 
______________________________________________________________________
Michael Sweet, Easy Software Products           mike at easysw dot com
Printing Software for UNIX                       http://www.easysw.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: Bugs/comments on 1.0.1

Posted by Justin Erenkrantz <ju...@erenkrantz.com>.
--On Tuesday, April 27, 2004 5:53 PM -0500 kfogel@collab.net wrote:

> However, if you want to stop prebuilding them, to simplify the release
> process, that's fine by me.

As Ben mentioned, I'm +1 on this.  -- justin

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: Bugs/comments on 1.0.1

Posted by kf...@collab.net.
Ben Reser <be...@reser.org> writes:
> Justin and I had discussed these info files in the past.  We both felt
> they shouldn't be included in the tarball.  Given that the only info
> files that we even have are the design documentation, which isn't that
> useful to most users, I don't see the point in bothering to prebuild
> these files.  Anyone that is likely to be interested in these files can
> read the .texi files directly or install makeinfo.
> 
> I'm also not entirely sure these files are up to date.  I haven't taken
> the time to read over them in detail to see what their status is.

They're up-to-date, in the sense that obsolete or wrong information
has been removed.  And they're actually very useful for someone trying
to understand the design of Subversion.  They do a good job of
presenting a high-level view of how things work.

However, if you want to stop prebuilding them, to simplify the release
process, that's fine by me.

-K

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: Bugs/comments on 1.0.1

Posted by Ben Reser <be...@reser.org>.
On Mon, Apr 19, 2004 at 09:28:49PM +0200, Erik Huelsmann wrote:
> >      2. "make install" will not work on a system without makeinfo
> >         on it.
> 
> I guess this too is a point for build-system adjustment. However using the
> the tarball, this will not be an issue, since pre-built info files are
> distributed with it.

This isn't entirely true.  If you use the tarball and do make clean it
will remove these files.  Thus creating the issue even for tarball
users.  In fact, I know it does this because I use make clean to get rid
of the tarball generated files, which (until 1.0.2) had a slightly
different naming scheme than newer makeinfo's created.

Justin and I had discussed these info files in the past.  We both felt
they shouldn't be included in the tarball.  Given that the only info
files that we even have are the design documentation, which isn't that
useful to most users, I don't see the point in bothering to prebuild
these files.  Anyone that is likely to be interested in these files can
read the .texi files directly or install makeinfo.

I'm also not entirely sure these files are up to date.  I haven't taken
the time to read over them in detail to see what their status is.

-- 
Ben Reser <be...@reser.org>
http://ben.reser.org

"Conscience is the inner voice which warns us somebody may be looking."
- H.L. Mencken

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: Bugs/comments on 1.0.1

Posted by Erik Huelsmann <e....@gmx.net>.
Hi Michael,

>      1. There is no easy way to disable the Apache module via the
>         configure script; what finally worked is:
> 
>             ./configure --without-apache --without-apxs --without-neon
>                 --disable-mod-activation
> 
>         I'm not sure if "--disable-mod-activation" is necessary, but
>         it would be nice to have a global "--disable-apache" option
>         to build without the Apache stuff.

This is a good point. I've also heard complaints that the configure options
aren't the most descriptive that can be. I guess your experience is nearly
the same.
 
>      2. "make install" will not work on a system without makeinfo
>         on it.

I guess this too is a point for build-system adjustment. However using the
the tarball, this will not be an issue, since pre-built info files are
distributed with it.

>      3. DB 4.0.x does not appear to work with the current Subversion;
>         I got a "function not implemented" error when creating a new
>         repository...  After upgrading our installed DB library to
>         4.2.52 everything seemed to work OK.  It might be worthwhile
>         to document that 4.0.x may not work at all...

There are two BDB issues which might give you this error. The first being a
custom built kernel mismatching the fact that BDB was or was not compiled to
run on an NPTL kernel (See the FAQ for a description). The other being your
Subversion linked against one BDB version and run against another.

Thanks for your input!

bye,

Erik.

-- 
"Sie haben neue Mails!" - Die GMX Toolbar informiert Sie beim Surfen!
Jetzt aktivieren unter http://www.gmx.net/info


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org