You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Files <fi...@poetryunlimited.com> on 2003/09/19 14:43:39 UTC
svn_version.h
In the interests of better serving the Mandrake community and allowing users to
compile their own RPMS w/o stepping on each other should they choose to share these
with each other, and to allow me to more easily identify why a compile might have
gone wrong, I would like to permission to use a dynamic patch to accomplish the
following ONLY during private Mandrake RPM compilation/bootstrapping - output from
svn --version follows:
-------------------------------------------------------------------------
svn, version 0.29.0 (dev kernel-2.4.21-0.13mdk-i686-Gnu/Linux-7093.1mdk build)
compiled Sep 19 2003, 10:05:39
Copyright (C) 2000-2003 CollabNet.
Subversion is open source software, see http://subversion.tigris.org/
The following repository access (RA) modules are available:
* ra_dav : Module for accessing a repository via WebDAV (DeltaV) protocol.
- handles 'http' schema
- handles 'https' schema
* ra_local : Module for accessing a repository on local disk.
- handles 'file' schema
* ra_svn : Module for accessing a repository using the svn network protocol.
- handles 'svn' schema
----------------------------------------------------------------------------
Traditional release builds would follow the normal naming convention.
Since the rpm compile spec I have built could conceivably be built on any rpm on a
non-Mandrake platform, I would want to help the users distinguish between their
private copies.
Perhaps at some later time, w/ additional review the private tarball builds would
also follow a similar convention, leaving only the relase versions standardized.
Just my 2 cents.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: svn_version.h
Posted by kf...@collab.net.
"Files" <fi...@poetryunlimited.com> writes:
> In the interests of better serving the Mandrake community and
> allowing users to compile their own RPMS w/o stepping on each other
> should they choose to share these with each other, and to allow me
> to more easily identify why a compile might have gone wrong, I would
> like to permission to use a dynamic patch to accomplish the
> following ONLY during private Mandrake RPM compilation/bootstrapping
> - output from svn --version follows:
You mean the patch to do this would be applied as part of the Mandrake
pkg build process? I think that's fine. You could even make the
additional information more verbose, so it's totally self-explanatory
and clear that it's about a Mandrake RPM build, if you want.
Just my $0.02,
-Karl
> -------------------------------------------------------------------------
>
> svn, version 0.29.0 (dev kernel-2.4.21-0.13mdk-i686-Gnu/Linux-7093.1mdk build)
> compiled Sep 19 2003, 10:05:39
>
> Copyright (C) 2000-2003 CollabNet.
> Subversion is open source software, see http://subversion.tigris.org/
>
> The following repository access (RA) modules are available:
>
> * ra_dav : Module for accessing a repository via WebDAV (DeltaV) protocol.
> - handles 'http' schema
> - handles 'https' schema
> * ra_local : Module for accessing a repository on local disk.
> - handles 'file' schema
> * ra_svn : Module for accessing a repository using the svn network protocol.
> - handles 'svn' schema
> ----------------------------------------------------------------------------
>
> Traditional release builds would follow the normal naming convention.
>
> Since the rpm compile spec I have built could conceivably be built on any rpm on a
> non-Mandrake platform, I would want to help the users distinguish between their
> private copies.
>
> Perhaps at some later time, w/ additional review the private tarball builds would
> also follow a similar convention, leaving only the relase versions standardized.
>
> Just my 2 cents.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org