On Monday 8 November 1999, at 17 h 26, the keyboard of
[EMAIL PROTECTED] wrote:
> You say there's no way in Unix to set a system-wide env variable.Still,
> since this is about Debian, wouldn't it be possible to mandate in the
> policy that each shell would source a common file that sets up env
>
On Monday 8 November 1999, at 14 h 31, the keyboard of "Ean R . Schuessler"
<[EMAIL PROTECTED]> wrote:
> is worth implementing. If you are strapped for time or are simply less
> interested then maybe we should look to somebody else.
I have enough time (I hope so) until potato is released. And I
On Mon, Nov 08, 1999 at 02:57:39PM +0100, Stephane Bortzmeyer wrote:
> Any volunteer to serve as the editor? It means writing the policy (not a lot
> of characters/lines but every word has to be carefully choosen), merging
> patches, patching the packages to test if the policy is realistic, sendi
On Mon, Nov 08, 1999 at 05:26:55PM +0100, [EMAIL PROTECTED] wrote:
> > - ease of use for new users (no .bashrc to edit) and for the sysadmin
> > (there is no way in Unix to set a system-wide env. variable), -
> > consistency between a shell into xterm ran by Gnome, a shell made after
> > a telnet/r
On Mon, Nov 08, 1999 at 02:44:04PM +0100, Stephane Bortzmeyer wrote:
> On Saturday 6 November 1999, at 18 h 14, the keyboard of "Ean R . Schuessler"
> <[EMAIL PROTECTED]> wrote:
>
> > I do understand that Debian policy discourages the concept of a
> > program requiring that an environment variabl
On Saturday 6 November 1999, at 18 h 14, the keyboard of "Ean R . Schuessler"
<[EMAIL PROTECTED]> wrote:
> I know that it is a bit late in the game to get this concept into
> freeze
[No longer an issue.]
> If this idea is recieved favorably perhaps it and some other
> formalizations can be fol
On Sunday 7 November 1999, at 15 h 30, the keyboard of Stefan Gybas
<[EMAIL PROTECTED]> wrote:
> While we are at it: I already expressed my dislike for the naming scheme
> in the policy (lib-X-java) which is taken from C libraries.
This is a more general Policy issue. See bug #41113.
On Sunday 7 November 1999, at 7 h 40, the keyboard of Christopher Cobb
<[EMAIL PROTECTED]> wrote:
> 1) The global CLASSPATH environmental variable never worked for me. I have
> too
> many different versions of JVMs (blackdown, ibm, kaffe, 1.1, 1.2)
Yes, that the major pain with most Java envi
On Saturday 6 November 1999, at 18 h 14, the keyboard of "Ean R . Schuessler"
<[EMAIL PROTECTED]> wrote:
> I do understand that Debian policy discourages the concept of a
> program requiring that an environment variable be set in order to
> operate sanely.
Note there are several reasons to do s
On Sun, Nov 07, 1999 at 03:30:07PM +0100, Stefan Gybas wrote:
> While we are at it: I already expressed my dislike for the naming scheme
> in the policy (lib-X-java) which is taken from C libraries. I propose to
> use the scheme from Phyton instead (java-X). What do other people think
> about this?
"Ean R . Schuessler" wrote:
> The best advice is perhaps to follow what policy actually states as
> the technique for dealing with programs that require an environment
> setting, a wrapper script. It is fairly trivial (1 line of shell code)
> to read in a list of configured classpaths from a folde
Comments:
1) The global CLASSPATH environmental variable never worked for me. I have too
many different versions of JVMs (blackdown, ibm, kaffe, 1.1, 1.2) that
I generally always set up an application-specific classpath within an
application-specific invocation script.
2) Even application-specif
I agree with most of your ideas, but I guess it's better to separate the
classpath required for the vm's, libraries and 'applications' (in the meaning
of java programs with main classes). The idea is to create a dependency system
for the classpaths definitions.
As an example, assume the follow
I have been giving a lot of thought to the policy that Stephane has
proposed. While I certainly appreciate the sentiment that has caused
him to push for adoption so strongly I still am not wholly satisfied
with the direction of his efforts.
I do understand that Debian policy discourages the concep
14 matches
Mail list logo
