On Tue, Jun 17, 2003 at 07:51:00PM -0400, Colin Walters wrote:
> @@ -7349,11 +7352,13 @@
>
>
>
> - Thus, every program that launches an editor or pager must
> - use the EDITOR or PAGER environment variable to determine
> - the editor or pager the user wishes to use
Ok, discussion turned up two problems, fixable by changing two words:
Web browsers
Some programs have the ability to launch a web browser to display an URL.
Since there are lots of different web browsers available in the Debian
distribution, the system administrator an
Package: debian-policy
Version: 3.5.10.0+cvs20030617
Severity: normal
Hi,
The following patch attempts to codify the current practice wrt
integrated environments (can anyone think of a better term? I just sort
of made that up). There should be no changes required to programs as
far as I know, th
On Tue, 2003-06-17 at 06:50, Andrew Suffield wrote:
> When I do it, I ignore what policy says and do what works. That means
> the build target is a no-op
This, of course, has the disadvantage of making the build target
useless.
> (or possibly an alias for build-arch)
Then it seems to me what y
On Tue, 2003-06-17 at 16:58, Bill Allombert wrote:
> If browser is a per-user preference, this should be a constant value for
> a particular user if he has not set the preference, and letting each
> programs start their browser of choice should be wrong. Debian needs to
> be consistant.
Sure, Deb
On Tue, Jun 17, 2003 at 04:25:04PM -0400, Colin Walters wrote:
> On Tue, 2003-06-17 at 15:40, Bill Allombert wrote:
>
> > Then as long as it is a per-user decision and not a per launcher
> > program, I cannot find anything wrong with Joey proposal.
>
> The only problem is that Joey's proposal mak
On Tue, 2003-06-17 at 15:40, Bill Allombert wrote:
> Then as long as it is a per-user decision and not a per launcher
> program, I cannot find anything wrong with Joey proposal.
The only problem is that Joey's proposal makes programs with a preferred
browser buggy.
> Users have already a way to
On Tue, Jun 17, 2003 at 02:30:12PM -0400, Colin Walters wrote:
> On Tue, 2003-06-17 at 06:31, Bill Allombert wrote:
>
> > Then I have a question: If a user use both KDE and GNOME stuff in a,
> > say, KDE environment, should x-www-browser always launch konqueror
> > or have GNOME programs launch th
On Tue, 2003-06-17 at 06:31, Bill Allombert wrote:
> Then I have a question: If a user use both KDE and GNOME stuff in a,
> say, KDE environment, should x-www-browser always launch konqueror
> or have GNOME programs launch the GNOME browser ?
I'm not sure what you mean; x-www-browser is just a sy
On Mon, Jun 16, 2003 at 07:40:34PM -0400, Colin Walters wrote:
>
> Well, probably the main reason we haven't hit this before is that most
> people don't bother to do a proper arch/indep split in their packages,
> and just stuff everything into Build-Depends.
That is not true, look at bug #148932
On Mon, Jun 16, 2003 at 07:40:34PM -0400, Colin Walters wrote:
> > As I've said before: Policy is either meant to document current
> > practice or it's not. If it is, then it's wrong because the de facto
> > implementation of build-depends disagrees with it _and always has
> > done_ (or at least,
On Mon, Jun 16, 2003 at 07:27:32PM -0400, Colin Walters wrote:
> It is broken. The whole point of an integrated environment is that it's
> integrated. When I choose a theme, it's used by every application.
> When I pick an application to handle a certain file type, it's handled
> by all of them.
12 matches
Mail list logo
