Dale Scheetz wrote:
> It was my understanding that, like the man and info transitions, these
> problems are resolved by giving the tools the knowledge of the dual
> locations. Our current binary dependencie scheme is sufficient to deal
> with "incremental upgrades". Those packages that use the new
[Reference: bug#43702]
I have had a request for a postgresql package with multibyte support.
Such support would enable postgresql to store data in different character
sets, so that data in Russian, Greek, Chinese or other scripts could be
stored and sorted properly.
There are several issues that
> > It worries me that we're going to become *very* dependent on a
> > specific version of make all of a sudden.
>
> Why? Where? The only thing that's GNU make specific is the variable
> defintion as a dependency, i.e. the suggested implementation of the
> build-debug target. But that's only a rec
On Wed, Sep 01, 1999 at 10:40:38AM +0200, Andreas Jellinghaus wrote:
> > This is common enough... should we perhaps create a system wide file, that
> > maps default {user,group}names to local {user,group}names?
> >
> > eg, in /etc/local_names:
> > mysql mysql
> > ups ups2
>
> no, please do
On Tue, 31 Aug 1999, Raphael Hertzog wrote:
> No problem, but you could try to do something realistic and logical.
I did. I read policy, asked base-passwd maintainer for static ids and got
no response at all. Then I asked here, in the hope to get things in order,
what we do right now, by this dis
> It worries me that we're going to become *very* dependent on a
> specific version of make all of a sudden.
Why? Where? The only thing that's GNU make specific is the variable
defintion as a dependency, i.e. the suggested implementation of the
build-debug target. But that's only a recommendation
> This is the final form (or, at least, I am done with this). I am
> forwarding this to bugs.debian.org
My ok again for the second variant.
Roman
> Should these packages built with BUILD_DEBUG turned on have a
> different name (i.e. libgtk1.2-dbg) than the standard packages? Is
> there an easy way to do this other than replicating control file
> entries?
Hmm... I'd say they shouldn't. They have the same functionality as the
non-debug packa
> Umm, since the intent is not to make the old way of doing things
> incorrect, we can do one of two things. Here are psuedo patches that
> detail the approaches. (I personally prefer the second approach).
The second one looks fine (except some typos).
Roman
"Joseph" == Joseph Carter <[EMAIL PROTECTED]> writes:
Joseph> Apache defaults to having /doc readable by only localhost, but
Actually its still world-browsable, since thats easiest (and policy
implies it). There are open bugs against this though.
netgod
i'm trying to convi
On Thu, Sep 02, 1999 at 12:17:35AM +1000, Anthony Towns wrote:
> > It was my understanding that this situation could be resolved in the same
> > fashion that the man and info transitions were. By making the docs viewing
> > programs aware of both the old and new locations, and back porting them
> >
Ben Collins <[EMAIL PROTECTED]> writes:
> On Wed, Sep 01, 1999 at 04:47:37PM -0700, Chris Waters wrote:
> > A simpler (though less comprehensive) solution would be to allow some
> > way to pass the -g flag explicitly, through standardized variables.
> > Something like:
> >
> > CC_DEBUG=-g dpkg-
On Wed, Sep 01, 1999 at 04:47:37PM -0700, Chris Waters wrote:
> Ben Collins <[EMAIL PROTECTED]> writes:
>
> > I wondered if anyone else has an opionion on which of these to choose.
> > Either one works for me, but I think the first one is probably needed
> > since some builds just can't be changed
13 matches
Mail list logo
