Hi folks!
I am not involved in creating the EAPI 2 draft but I am interested in
the discussion and would like to track the technical evolution but
this seams nearly impossible as you're not able to agree on a public
draft document.
* Ciaran McCreesh [EMAIL PROTECTED] [080911 20:02]:
On Mon, 08
On Fri, 12 Sep 2008 08:28:52 +0200
Michael Hammer [EMAIL PROTECTED] wrote:
- An official (by the council accepted) VCS repo (a la git) for the
document (EAPI draft or even the PMS spec?)
Uh, already exists.
- An interface (mailing address) where everyone interested can submit
a patch for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Donnie Berkholz wrote:
On 12:46 Sun 07 Sep , Marcus D. Hanwell wrote:
I personally agree with several others who have replied to this thread.
The reduction in lines of code/characters seems to introduce an uglier
syntax which is harder to
Icedtea has two release tracks. One for the 1.7 OpenJDK code base and
one for the 1.6 code base. They have independent version numbering so
they can have collisions. By moving the slot to the file name we could
have icedtea-1.2:1.6.ebuildN and icedtea-1.2:1.7.ebuildN. This
particular situation
Ciaran McCreesh [EMAIL PROTECTED] wrote:
On Tue, 9 Sep 2008 22:14:57 -0400
Jim Ramsay [EMAIL PROTECTED] wrote:
I was personally expecting to see some sort of section called
EAPI-1 that contains something like:
EAPI-1 consists of EAPI-0 with the following features added...
Have a look
On Fri, 12 Sep 2008 14:14:51 -0400
Jim Ramsay [EMAIL PROTECTED] wrote:
Unrelated topic: What packages are actually required to 'make
pms.pdf' so I can actually read it? I get:
Have a look at the dependencies for app-doc/pms.
--
Ciaran McCreesh
signature.asc
Description: PGP signature
On Fri, 12 Sep 2008 21:12:30 +0300
Petteri Räty [EMAIL PROTECTED] wrote:
Icedtea has two release tracks. One for the 1.7 OpenJDK code base and
one for the 1.6 code base. They have independent version numbering so
they can have collisions. By moving the slot to the file name we
could have
On 14:56 Fri 12 Sep , Doug Goldstein wrote:
Petteri Räty wrote:
Icedtea has two release tracks. One for the 1.7 OpenJDK code base and
one for the 1.6 code base. They have independent version numbering so
they can have collisions. By moving the slot to the file name we could
have
Donnie Berkholz kirjoitti:
On 14:56 Fri 12 Sep , Doug Goldstein wrote:
Petteri Räty wrote:
Icedtea has two release tracks. One for the 1.7 OpenJDK code base and
one for the 1.6 code base. They have independent version numbering so
they can have collisions. By moving the slot to the file
On 22:21 Fri 12 Sep , Petteri Räty wrote:
I do know how to get around it, I did state that in my original email.
As it happens we are having a discussion on gentoo-java mailing list on
whether we should use icedtea-openjdk build.icedtea version.ebuild
or have different packages for
Donnie Berkholz kirjoitti:
On 22:21 Fri 12 Sep , Petteri Räty wrote:
I do know how to get around it, I did state that in my original email.
As it happens we are having a discussion on gentoo-java mailing list on
whether we should use icedtea-openjdk build.icedtea version.ebuild
or have
11 matches
Mail list logo
