Greg Stark <[EMAIL PROTECTED]> writes:
> There is a nice simple solution that would make our lives infinitely
> easier in lots of other ways: Build outside the source tree! This is
> how autoconf is intended to be used and it makes things a lot easier
> to manage.
Sure. Lots of packages do just t
Chris Waters <[EMAIL PROTECTED]> writes:
> Joey Hess <[EMAIL PROTECTED]> writes:
>
> > debian/rules clean is already required to reverse the effects of the build.
>
> In theory, yes. But unless you audit the .diff.gz, it's not
> necessarily obvious if this fails.
In fact there are packages
On Tue, Dec 14, 1999 at 01:28:21PM -0800, Darren wrote:
> It's a good point. How should we rewrite section 4.2 to say that it
> only refers to public libraries rather than internal libraries? And
> which parts do and don't? What about compiled Perl modules, for
> example? I don't know the answe
> >Yes, it's just in the packaging manual... yes, that is not policy... *yet*
Actually, the DPaM is policy, altough it contains some material that
ought not to be.
--
%%% Antti-Juhani Kaijanaho % [EMAIL PROTECTED] % http://www.iki.fi/gaia/ %%%
""
On Sun, 19 Dec 1999, Oliver Elphick wrote:
> [Forwarded to debian-policy for comments]
>
> "Juergen A. Erhard" wrote:
> >Package: python-pygresql
> >Version: 6.5.3-4
> >Severity: normal
> >
> >The upstream version of the pygresql package is 2.4, but the upstream
> >version number on t
[Forwarded to debian-policy for comments]
"Juergen A. Erhard" wrote:
>Package: python-pygresql
>Version: 6.5.3-4
>Severity: normal
>
>The upstream version of the pygresql package is 2.4, but the upstream
>version number on this .deb is 6.5.3. This is wrong.
>
>Yes, it's just in th
6 matches
Mail list logo
