On Tue, Nov 14, 2000 at 02:27:43PM +, Dave Swegen did utter:
> Hi! Over the past few months I've been trying out a number of CD
> players, and have been slightly annoyed by the fact that different
> players deal with local cddb databases in different ways, resulting in a
> number of (sometimes
On Wed, 22 Nov 2000, Anthony Towns wrote:
> You could also reasonably map all the maintainer scripts invocations of
> invoke-rc.d to no-ops in order to just leave all services running during
> an upgrade (rather than possibly shutting them down for an extended period,
> say).
This is what I'd reco
Let me start by saying that i am not in any way attached to this
specific amendment to policy. What i would like is to be able to
cause the files that are normally placed in the parent directory
while building a package to be placed instead in some other
directory. An environment variable would be
> "Wichert" == Wichert Akkerman <[EMAIL PROTECTED]> writes:
Wichert> Previously Eric Gillespie, Jr. wrote:
>> Does it? Why not just have dpkg override that final parameter
>> with $DEB_BUILD_DIR? If someone sets this variable, they
>> clearly want the files to go there and not
On Wed, 22 Nov 2000 17:39:48 + (UTC),
[EMAIL PROTECTED] (Wichert Akkerman) said:
> No tool should try to second-guess the user.
Eh? It isn't. The user *told* dpkg to do this by setting the
variable.
--
Eric Gillespie, Jr. <*> [EMAIL PROTECTED]
Software Developer
Progeny Linux Systems -
On Wed, Nov 22, 2000 at 05:04:32PM +0100, Wichert Akkerman wrote:
> How many times do I have to repeat that this is *NOT* a feature of the
> toolkit but of the fact that the path where the debs are made is
> explicitly given in each and every debian/rules file?
Explicitly? No -- none of my packa
Previously Eric Gillespie, Jr. wrote:
> Does it? Why not just have dpkg override that final parameter
> with $DEB_BUILD_DIR? If someone sets this variable, they clearly
> want the files to go there and not '..'.
No tool should try to second-guess the user.
Wichert.
--
On 22-Nov-2000 Wichert Akkerman wrote:
> Previously Chris Waters wrote:
>> I think Wichert was wrong in this case. I don't think policy should
>> be in charge of every minor feature of the toolkit, especially not
>> optional features.
>
> How many times do I have to repeat that this is *NOT* a f
Previously Chris Waters wrote:
> I think Wichert was wrong in this case. I don't think policy should
> be in charge of every minor feature of the toolkit, especially not
> optional features.
How many times do I have to repeat that this is *NOT* a feature of the
toolkit but of the fact that the pa
On Sat, Nov 18, 2000 at 01:00:04PM -0200, Henrique M Holschuh wrote:
> > actually. For restart/restart-if-running it's something of an
> > attempt to DWIM (if I say "restart" out of runlevel, I probably mean
> > "restart-if-running", so do that) but I don't see what other uses it
> > could have...
On Mon, Nov 20, 2000 at 10:37:03AM -0500, Eric Gillespie, Jr. wrote:
> I recently filed this wishlist bug
> (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=77153&repeatmerged=yes)
> against dpkg-dev, and Wichert told me to take it up with policy,
> so here i am.
> I think it would be nice if the
11 matches
Mail list logo
