Hallo Arnaud,
* Arnaud Vandyck wrote:
>So (even if I'm not yet a DD), I second your proposal if point 3 is
>respected.
s/(.*),//
-> Seems that I got my one and only DD approval 'the other way' :(
On the other hand: Congratulation!
Jan
--
Jan Schulz [EMAIL PROTECTED]
Hallo Arnaud,
* Arnaud Vandyck wrote:
>Jan Schulz <[EMAIL PROTECTED]> wrote:
>> * Arnaud Vandyck wrote:
>So I did not follow all the thread. I appreciate the summary effort and
>after reading this mail I have no special argument to stop your proposal
>but I do not want to second it if it's a MUS
On Wed, 15 Oct 2003 18:04:32 +0200
Jan Schulz <[EMAIL PROTECTED]> wrote:
> Hallo Arnaud,
Hallo Jan,
> * Arnaud Vandyck wrote:
> >Same for me, wait until sarge is out and let's restart the discussions
> >about a new policy.
>
> Sorry, but that was exactly the reply I was *not* hoping for. IMO
In message: <[EMAIL PROTECTED]>
Jan Schulz <[EMAIL PROTECTED]> writes:
[a minor rant about how there's not much progress on Java in Debian]
I don't anything particularly useful to reply to the points that Jan
makes, largely because I've given up on Java per se as part of Debian.
The
Hi,
Maybe it would be a good idea to have different policies for different
levels of stability in Debian, i.e., different releases. Then we could
happily discuss and implement these new policies in sid without worrying
about sarge.
Sorry if this is a stupid, naive email, but that's what I'm here
Hallo Stefan,
only to the list...
* Stefan Gybas wrote:
>I also suggest to handle it this way. However, I think we can still make
>small changes to the Java Policy before sarge's release, e.g. remove the
>possibility to put Java classes in /usr/bin/ (using binfmt_misc). This
>would not affect
Hallo Arnaud,
* Arnaud Vandyck wrote:
>Same for me, wait until sarge is out and let's restart the discussions
>about a new policy.
Sorry, but that was exactly the reply I was *not* hoping for. IMO
there is enough discussion and the whole thing needs some testing. I'm
also willing to write most
Arnaud Vandyck wrote:
Same for me, wait until sarge is out and let's restart the discussions
about a new policy.
I also suggest to handle it this way. However, I think we can still make
small changes to the Java Policy before sarge's release, e.g. remove the
possibility to put Java classes in
Same for me, wait until sarge is out and let's restart the discussions
about a new policy.
On Wed, 15 Oct 2003 12:21:37 +1000
Ben Burton <[EMAIL PROTECTED]> wrote:
>
> Hi.
>
> > There seems to be no more questions, but unfortunatelly nonone has
> > said something like 'do it' or 'file bugs wi
Hallo Ben,
* Ben Burton wrote:
>My only comment is that since sarge is purportedly so close to freeze
>and since this is more or less a complete policy rewrite, I think we
>should keep current java policy until after sarge.
Yes, thats sensible :) Anyway, as I stated, I can't see a problem
in
Hi.
> There seems to be no more questions, but unfortunatelly nonone has
> said something like 'do it' or 'file bugs with patches' or 'go
> testing' or whatever until now.
My only comment is that since sarge is purportedly so close to freeze
and since this is more or less a complete policy rewri
Hallo,
There seems to be no more questions, but unfortunatelly nonone has
said something like 'do it' or 'file bugs with patches' or 'go
testing' or whatever until now.
I'm a little scared to go on, and ask Stefan for the temporary
inclusion of the findjava and other scripts in java-common or the
12 matches
Mail list logo
