From lordblick at gmail.com  Thu Jul  2 03:25:23 2015
From: lordblick at gmail.com (LordBlick)
Date: Thu, 02 Jul 2015 03:25:23 +0200
Subject: python-cssselect.spec up
Message-ID: <55949303.7000106@gmail.com>

Hello,
Here is version update, please apply attachment to spec.
Any suggestions appreciated, if no one, please commit.

-- 
Best Regards,
LordBlick
-------------- next part --------------
A non-text attachment was scrubbed...
Name: up.patch
Type: text/x-patch
Size: 871 bytes
Desc: not available
URL: </mailman/pipermail/pld-devel-en/attachments/20150702/69e28d51/attachment.bin>

From baggins at pld-linux.org  Thu Jul  9 21:02:31 2015
From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=)
Date: Thu, 9 Jul 2015 21:02:31 +0200
Subject: Policy change regarding dependency breakage
Message-ID: <20150709190230.GA8338@dhcppc27.lan>

TL;DR I you build dependency breking package, you have to fix broken
deps or the package will be removed.


I don't have time nor will anymore to fix averyones breakage, from now
on I am not going to fix someone elses dependency breakage. If you send
a dependency breaker to th-test you have to take care of rebuilding
packages that got broken. If the deps are not fixed after a month I will
remove and downgrade package that broke deps.

Current example: ocaml.

-- 
Jan R?korajski                    | PLD/Linux
SysAdm | baggins<at>pld-linux.org | http://www.pld-linux.org/


From jajcus at jajcus.net  Thu Jul  9 22:25:25 2015
From: jajcus at jajcus.net (Jacek Konieczny)
Date: Thu, 09 Jul 2015 22:25:25 +0200
Subject: Policy change regarding dependency breakage
In-Reply-To: <20150709190230.GA8338@dhcppc27.lan>
References: <20150709190230.GA8338@dhcppc27.lan>
Message-ID: <559ED8B5.20204@jajcus.net>

On 2015-07-09 21:02, Jan R?korajski wrote:
> TL;DR I you build dependency breking package, you have to fix broken
> deps or the package will be removed.

Is there a chance for some kind of notifications when the dependencies
are broken? That is not always obvious when one does not have all
possible Th packages installed.

Jacek



From baggins at pld-linux.org  Thu Jul  9 22:26:57 2015
From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=)
Date: Thu, 9 Jul 2015 22:26:57 +0200
Subject: Policy change regarding dependency breakage
In-Reply-To: <559ED8B5.20204@jajcus.net>
References: <20150709190230.GA8338@dhcppc27.lan>
 <559ED8B5.20204@jajcus.net>
Message-ID: <20150709202657.GB8338@dhcppc27.lan>

On Thu, 09 Jul 2015, Jacek Konieczny wrote:

> On 2015-07-09 21:02, Jan R?korajski wrote:
> > TL;DR I you build dependency breking package, you have to fix broken
> > deps or the package will be removed.
> 
> Is there a chance for some kind of notifications when the dependencies
> are broken? That is not always obvious when one does not have all
> possible Th packages installed.

Current state is always available at:
http://ep09.pld-linux.org/~pldth/main-ready-test.txt

-- 
Jan R?korajski                    | PLD/Linux
SysAdm | baggins<at>pld-linux.org | http://www.pld-linux.org/


From glen at pld-linux.org  Mon Jul 13 09:18:56 2015
From: glen at pld-linux.org (=?UTF-8?B?RWxhbiBSdXVzYW3DpGU=?=)
Date: Mon, 13 Jul 2015 10:18:56 +0300
Subject: Policy change regarding dependency breakage
In-Reply-To: <20150709190230.GA8338@dhcppc27.lan>
References: <20150709190230.GA8338@dhcppc27.lan>
Message-ID: <55A36660.1050406@pld-linux.org>

On 09.07.2015 22:02, Jan R?korajski wrote:
>   If the deps are not fixed after a month I will
> remove and downgrade package that broke deps.

as long as this process does not involve epoch bumping.

-- 
glen



From mike at altlinux.org  Mon Jul 13 12:38:06 2015
From: mike at altlinux.org (Michael Shigorin)
Date: Mon, 13 Jul 2015 13:38:06 +0300
Subject: Policy change regarding dependency breakage
In-Reply-To: <20150709190230.GA8338@dhcppc27.lan>
References: <20150709190230.GA8338@dhcppc27.lan>
Message-ID: <20150713103806.GG26912@imap.altlinux.org>

On Thu, Jul 09, 2015 at 09:02:31PM +0200, Jan R?korajski wrote:
> TL;DR I you build dependency breking package, you have to fix
> broken deps or the package will be removed.

ALT gained both major PITA (for some time) and peace of mind
(ever since) when build tasks increasing unmets number were
forbidden.  It turned out that even an "unstable" repo with
no broken deps is much more suitable for actual "living".

HTH

-- 
?---- WBR, Michael Shigorin / http://altlinux.org
??------ http://opennet.ru / http://anna-news.info


From glen at pld-linux.org  Mon Jul 13 15:41:01 2015
From: glen at pld-linux.org (=?UTF-8?B?RWxhbiBSdXVzYW3DpGU=?=)
Date: Mon, 13 Jul 2015 16:41:01 +0300
Subject: [packages/imsettings] - fix xinitrc script perms - rel 3
In-Reply-To: <697931cdc57afa9b30392073cb727097dfdc79c8_refs_heads_master@pld-linux.org>
References: <d9ef268523c0e8209b8e88005d7e4c870e1e4afa_refs_heads_master@pld-linux.org>
 <697931cdc57afa9b30392073cb727097dfdc79c8_refs_heads_master@pld-linux.org>
Message-ID: <55A3BFED.8080704@pld-linux.org>

On 11.07.2015 13:02, baggins wrote:
> commit 697931cdc57afa9b30392073cb727097dfdc79c8
> Author: Jan R?korajski <baggins at pld-linux.org>
> Date:   Sat Jul 11 12:02:38 2015 +0200
>
>      - fix xinitrc script perms
>      - rel 3
>
>   imsettings.spec | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
> ---
> diff --git a/imsettings.spec b/imsettings.spec
> index 556547a..fe6f005 100644
> --- a/imsettings.spec
> +++ b/imsettings.spec
> @@ -8,7 +8,7 @@ Summary:	Delivery framework for general Input Method configuration
>   Summary(pl.UTF-8):	Szkielet do og?lnej konfiguracji method wprowadzania znak?w
>   Name:		imsettings
>   Version:	1.6.8
> -Release:	2
> +Release:	3
>   License:	LGPL v2+
>   Group:		Applications/System
>   Source0:	https://bitbucket.org/tagoh/imsettings/downloads/%{name}-%{version}.tar.bz2
> @@ -348,7 +348,7 @@ rm -rf $RPM_BUILD_ROOT
>   %defattr(644,root,root,755)
>   %doc AUTHORS ChangeLog NEWS README
>   
> -%{_sysconfdir}/X11/xinit/xinitrc.d/50-xinput.sh
> +%attr(755,root,root) %{_sysconfdir}/X11/xinit/xinitrc.d/50-xinput.sh
>   %{_sysconfdir}/X11/xinit/xinput.d/*.conf
>   %{_sysconfdir}/xdg/autostart/imsettings-start.desktop
>

this is wrong. these scripts there are sourced, not executed

if you change is to introduce /bin/sh dependency, then just do chmod in 
%install, but leave %files as 0640

the same applies to systemd,sabayon spec changes of yours

-- 
glen



From baggins at pld-linux.org  Mon Jul 13 20:02:29 2015
From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=)
Date: Mon, 13 Jul 2015 20:02:29 +0200
Subject: [packages/imsettings] - fix xinitrc script perms - rel 3
In-Reply-To: <55A3BFED.8080704@pld-linux.org>
References: <d9ef268523c0e8209b8e88005d7e4c870e1e4afa_refs_heads_master@pld-linux.org>
 <697931cdc57afa9b30392073cb727097dfdc79c8_refs_heads_master@pld-linux.org>
 <55A3BFED.8080704@pld-linux.org>
Message-ID: <20150713180229.GA2955@tachikoma>

On Mon, 13 Jul 2015, Elan Ruusam?e wrote:

> On 11.07.2015 13:02, baggins wrote:
> > commit 697931cdc57afa9b30392073cb727097dfdc79c8
> > Author: Jan R?korajski <baggins at pld-linux.org>
> > Date:   Sat Jul 11 12:02:38 2015 +0200
> >
> >      - fix xinitrc script perms
> >      - rel 3
> >
> >   imsettings.spec | 4 ++--
> >   1 file changed, 2 insertions(+), 2 deletions(-)
> > ---
> > diff --git a/imsettings.spec b/imsettings.spec
> > index 556547a..fe6f005 100644
> > --- a/imsettings.spec
> > +++ b/imsettings.spec
> > @@ -8,7 +8,7 @@ Summary:	Delivery framework for general Input Method configuration
> >   Summary(pl.UTF-8):	Szkielet do og?lnej konfiguracji method wprowadzania znak?w
> >   Name:		imsettings
> >   Version:	1.6.8
> > -Release:	2
> > +Release:	3
> >   License:	LGPL v2+
> >   Group:		Applications/System
> >   Source0:	https://bitbucket.org/tagoh/imsettings/downloads/%{name}-%{version}.tar.bz2
> > @@ -348,7 +348,7 @@ rm -rf $RPM_BUILD_ROOT
> >   %defattr(644,root,root,755)
> >   %doc AUTHORS ChangeLog NEWS README
> >   
> > -%{_sysconfdir}/X11/xinit/xinitrc.d/50-xinput.sh
> > +%attr(755,root,root) %{_sysconfdir}/X11/xinit/xinitrc.d/50-xinput.sh
> >   %{_sysconfdir}/X11/xinit/xinput.d/*.conf
> >   %{_sysconfdir}/xdg/autostart/imsettings-start.desktop
> >
> 
> this is wrong. these scripts there are sourced, not executed
> 
> if you change is to introduce /bin/sh dependency, then just do chmod in 
> %install, but leave %files as 0640
> 
> the same applies to systemd,sabayon spec changes of yours

This is not wrong, they are sourced iff the script is executable.

-- 
Jan R?korajski                    | PLD/Linux
SysAdm | baggins<at>pld-linux.org | http://www.pld-linux.org/


From glen at pld-linux.org  Tue Jul 14 00:19:54 2015
From: glen at pld-linux.org (=?UTF-8?B?RWxhbiBSdXVzYW3DpGU=?=)
Date: Tue, 14 Jul 2015 01:19:54 +0300
Subject: [packages/imsettings] - fix xinitrc script perms - rel 3
In-Reply-To: <20150713180229.GA2955@tachikoma>
References: <d9ef268523c0e8209b8e88005d7e4c870e1e4afa_refs_heads_master@pld-linux.org>
 <697931cdc57afa9b30392073cb727097dfdc79c8_refs_heads_master@pld-linux.org>
 <55A3BFED.8080704@pld-linux.org> <20150713180229.GA2955@tachikoma>
Message-ID: <55A4398A.5050905@pld-linux.org>

On 13.07.2015 21:02, Jan R?korajski wrote:
>> >this is wrong. these scripts there are sourced, not executed
>> >
>> >if you change is to introduce /bin/sh dependency, then just do chmod in
>> >%install, but leave %files as 0640
>> >
>> >the same applies to systemd,sabayon spec changes of yours
> This is not wrong, they are sourced iff the script is executable.

well. *that* is wrong.

other system locations that source *.sh (checked /etc/shrc.d, 
/etc/profile.d), do not require execute bit

and in fact you should not execute these, as they may require additional 
env (which is present when sourced from main script)


...

and even the extra check for "x" bit  to avoid executing backups, blows 
up, as vim backups (*~) have exactly the same permissions as original 
(if possible) and *.sh glob should exclude backups.

-- 
glen



From glen at pld-linux.org  Wed Jul 15 14:17:27 2015
From: glen at pld-linux.org (=?ISO-8859-1?Q?Elan_Ruusam=E4e?=)
Date: Wed, 15 Jul 2015 15:17:27 +0300
Subject: php 7.0
Message-ID: <55A64F57.9000104@pld-linux.org>

hi

i'm wondering how to package php 7.0

earlier versions were packaged as phpXY, i.e php52, php53, .. php56

some concern was risen (by qboosh), that what if php really reaches 
version 70 (icu for example),
that would lead to some ambiguity.

however building with 7.0 suffix, means build scripts will break that 
assume it's without dot.
it's probably fixable, but with some extra effort.

what's your opinions?

-- 
glen



From arekm at maven.pl  Wed Jul 15 21:41:46 2015
From: arekm at maven.pl (Arkadiusz =?utf-8?q?Mi=C5=9Bkiewicz?=)
Date: Wed, 15 Jul 2015 21:41:46 +0200
Subject: php 7.0
In-Reply-To: <55A64F57.9000104@pld-linux.org>
References: <55A64F57.9000104@pld-linux.org>
Message-ID: <201507152141.46860.arekm@maven.pl>

On Wednesday 15 of July 2015, Elan Ruusam?e wrote:
> hi
> 
> i'm wondering how to package php 7.0
> 
> earlier versions were packaged as phpXY, i.e php52, php53, .. php56
> 
> some concern was risen (by qboosh), that what if php really reaches
> version 70 (icu for example),
> that would lead to some ambiguity.

Go with php70. If php reaches 70 we will use php700 obviously.

-- 
Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org )


From baggins at pld-linux.org  Wed Jul 15 23:13:19 2015
From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=)
Date: Wed, 15 Jul 2015 23:13:19 +0200
Subject: php 7.0
In-Reply-To: <55A64F57.9000104@pld-linux.org>
References: <55A64F57.9000104@pld-linux.org>
Message-ID: <20150715211318.GA855@tachikoma.lan>

On Wed, 15 Jul 2015, Elan Ruusam?e wrote:

> hi
> 
> i'm wondering how to package php 7.0
> 
> earlier versions were packaged as phpXY, i.e php52, php53, .. php56
> 
> some concern was risen (by qboosh), that what if php really reaches 
> version 70 (icu for example),
> that would lead to some ambiguity.
> 
> however building with 7.0 suffix, means build scripts will break that 
> assume it's without dot.
> it's probably fixable, but with some extra effort.
> 
> what's your opinions?

What exactly is the problem? I dont's see any with naming package php70.

-- 
Jan R?korajski                    | PLD/Linux
SysAdm | baggins<at>pld-linux.org | http://www.pld-linux.org/


From glen at pld-linux.org  Thu Jul 16 10:30:49 2015
From: glen at pld-linux.org (=?UTF-8?B?RWxhbiBSdXVzYW3DpGU=?=)
Date: Thu, 16 Jul 2015 11:30:49 +0300
Subject: php 7.0
In-Reply-To: <20150715211318.GA855@tachikoma.lan>
References: <55A64F57.9000104@pld-linux.org>
 <20150715211318.GA855@tachikoma.lan>
Message-ID: <55A76BB9.30000@pld-linux.org>

On 16.07.2015 00:13, Jan R?korajski wrote:
> On Wed, 15 Jul 2015, Elan Ruusam?e wrote:
>
>> hi
>>
>> i'm wondering how to package php 7.0
>>
>> earlier versions were packaged as phpXY, i.e php52, php53, .. php56
>>
>> some concern was risen (by qboosh), that what if php really reaches
>> version 70 (icu for example),
>> that would lead to some ambiguity.
>>
>> however building with 7.0 suffix, means build scripts will break that
>> assume it's without dot.
>> it's probably fixable, but with some extra effort.
>>
>> what's your opinions?
> What exactly is the problem? I dont's see any with naming package php70.
>

quote:
"some concern was risen (by qboosh), that what if php really reaches 
version 70 (icu for example), that would lead to some ambiguity."

so php 7.0.0 and 70.0 would be both named as "php70".

anyway, considering arekm note, sticking with php70 for now then.

-- 
glen



From gotar at polanet.pl  Thu Jul 16 11:23:02 2015
From: gotar at polanet.pl (Tomasz Pala)
Date: Thu, 16 Jul 2015 11:23:02 +0200
Subject: php 7.0
In-Reply-To: <55A64F57.9000104@pld-linux.org>
References: <55A64F57.9000104@pld-linux.org>
Message-ID: <20150716092302.GA18926@polanet.pl>

On Wed, Jul 15, 2015 at 15:17:27 +0300, Elan Ruusam?e wrote:

> some concern was risen (by qboosh), that what if php really reaches 
> version 70 (icu for example),

If it reaches version 70, there should be version 56 before that.
Then we could probably drop/ignore these versions as PHP until then will
be hopefuly forgotten language.

-- 
Tomasz Pala <gotar at pld-linux.org>


From lordblick at gmail.com  Thu Jul 16 18:52:09 2015
From: lordblick at gmail.com (LordBlick)
Date: Thu, 16 Jul 2015 18:52:09 +0200
Subject: blueman spec - new release up
Message-ID: <55A7E139.3040904@gmail.com>

-up to 2.0 release (source changed to new dev team on github)
Please apply attachment to spec.
Any suggestions appreciated, if no one, please commit.

-- 
Best Regards,
LordBlick
-------------- next part --------------
A non-text attachment was scrubbed...
Name: relup.patch
Type: text/x-patch
Size: 4952 bytes
Desc: not available
URL: </mailman/pipermail/pld-devel-en/attachments/20150716/dfb72eca/attachment.bin>

From glen at pld-linux.org  Fri Jul 17 09:34:03 2015
From: glen at pld-linux.org (=?ISO-8859-1?Q?Elan_Ruusam=E4e?=)
Date: Fri, 17 Jul 2015 10:34:03 +0300
Subject: blueman spec - new release up
In-Reply-To: <55A7E139.3040904@gmail.com>
References: <55A7E139.3040904@gmail.com>
Message-ID: <55A8AFEB.6020001@pld-linux.org>

On 16.07.2015 19:52, LordBlick wrote:
> -up to 2.0 release (source changed to new dev team on github)
> Please apply attachment to spec.
> Any suggestions appreciated, if no one, please commit. 

applied. will push after build succeeds


-- 
glen



From lordblick at gmail.com  Fri Jul 17 22:32:19 2015
From: lordblick at gmail.com (LordBlick)
Date: Fri, 17 Jul 2015 22:32:19 +0200
Subject: blueman spec - new release up
In-Reply-To: <55A8AFEB.6020001@pld-linux.org>
References: <55A7E139.3040904@gmail.com> <55A8AFEB.6020001@pld-linux.org>
Message-ID: <55A96653.6030006@gmail.com>

In response to a message written on 17.07.2015, 09:34, from Elan Ruusam?e:
> On 16.07.2015 19:52, LordBlick wrote:
>> -up to 2.0 release (source changed to new dev team on github)
>> Please apply attachment to spec.
>> Any suggestions appreciated, if no one, please commit.
>
> applied. will push after build succeeds
With this commit builds without problems (including org.blueman.Applet.service):
https://github.com/blueman-project/blueman/commit/3ce97e90c9f1dbe53cb3363245343fdccf216592

-- 
Best Regards,
LordBlick


From glen at pld-linux.org  Sun Jul 19 16:24:25 2015
From: glen at pld-linux.org (=?UTF-8?B?RWxhbiBSdXVzYW3DpGU=?=)
Date: Sun, 19 Jul 2015 17:24:25 +0300
Subject: blueman spec - new release up
In-Reply-To: <55A96653.6030006@gmail.com>
References: <55A7E139.3040904@gmail.com> <55A8AFEB.6020001@pld-linux.org>
 <55A96653.6030006@gmail.com>
Message-ID: <55ABB319.1050509@pld-linux.org>

On 17.07.2015 23:32, LordBlick wrote:
> In response to a message written on 17.07.2015, 09:34, from Elan 
> Ruusam?e:
>> On 16.07.2015 19:52, LordBlick wrote:
>>> -up to 2.0 release (source changed to new dev team on github)
>>> Please apply attachment to spec.
>>> Any suggestions appreciated, if no one, please commit.
>>
>> applied. will push after build succeeds
> With this commit builds without problems (including 
> org.blueman.Applet.service):
> https://github.com/blueman-project/blueman/commit/3ce97e90c9f1dbe53cb3363245343fdccf216592 
>
>
but that does not apply to current codebase

btw, you can always fork pld package on github and suggest PR :)
https://github.com/pld-linux/blueman

-- 
glen



From glen at pld-linux.org  Sun Jul 26 15:23:36 2015
From: glen at pld-linux.org (=?UTF-8?B?RWxhbiBSdXVzYW3DpGU=?=)
Date: Sun, 26 Jul 2015 16:23:36 +0300
Subject: dkms & kernel-module-build
Message-ID: <55B4DF58.7040303@pld-linux.org>

hi

i think we need virtual provides for kernel-xx-module-build

$ rpm -qp --provides kernel-3.18-module-build-3.18.14-1.x86_64.rpm
kernel-3.18-module-build = 3:3.18.14-1

so, "kernel(module-build) = %{version}" ?

-- 
glen



From glen at pld-linux.org  Sun Jul 26 20:56:50 2015
From: glen at pld-linux.org (=?UTF-8?B?RWxhbiBSdXVzYW3DpGU=?=)
Date: Sun, 26 Jul 2015 21:56:50 +0300
Subject: IcedTea8
Message-ID: <55B52D72.4040101@pld-linux.org>

anyone working on IcedTea8?

seems that tomcat >= 7.0.53 fails to build with java6 or java7
(see tomcat at dev-7.0.55 branch for WIP)

-- 
glen




From jajcus at jajcus.net  Mon Jul 27 08:11:25 2015
From: jajcus at jajcus.net (Jacek Konieczny)
Date: Mon, 27 Jul 2015 08:11:25 +0200
Subject: IcedTea8
In-Reply-To: <55B52D72.4040101@pld-linux.org>
References: <55B52D72.4040101@pld-linux.org>
Message-ID: <55B5CB8D.1080002@jajcus.net>

On 2015-07-26 20:56, Elan Ruusam?e wrote:
> anyone working on IcedTea8?

None I know of, but it is time to package Java 8.

And probably it might be a better idea to build OpenJDK directly instead 
of using IcedTea8. Current OpenJDK should be buildable on its own, 
though probably without x32 support.

> seems that tomcat >= 7.0.53 fails to build with java6 or java7
> (see tomcat at dev-7.0.55 branch for WIP)

I guess there will be more and more such packages? But Java is so big 
and builds so long? I really don't have time for that. :-(

And a reminder: the oracle-java7 and oracle-java8 packages we have in 
PLD are not legally distributable ? the old Sun license 'for 
distributions' is gone and distributing Oracle Java with a Linux 
distribution is not allowed by its current license.

So, the only way to go is to prepare IcedTea8 or OpenJDK package.

Jacek



From glen at pld-linux.org  Mon Jul 27 08:32:57 2015
From: glen at pld-linux.org (=?windows-1252?Q?Elan_Ruusam=E4e?=)
Date: Mon, 27 Jul 2015 09:32:57 +0300
Subject: IcedTea8
In-Reply-To: <55B5CB8D.1080002@jajcus.net>
References: <55B52D72.4040101@pld-linux.org> <55B5CB8D.1080002@jajcus.net>
Message-ID: <55B5D099.7080406@pld-linux.org>

On 27.07.2015 09:11, Jacek Konieczny wrote:
> And a reminder: the oracle-java7 and oracle-java8 packages we have in 
> PLD are not legally distributable ? the old Sun license 'for 
> distributions' is gone and distributing Oracle Java with a Linux 
> distribution is not allowed by its current license. 

yes. it's removed from th.

-- 
glen



From glen at pld-linux.org  Mon Jul 27 08:33:34 2015
From: glen at pld-linux.org (=?windows-1252?Q?Elan_Ruusam=E4e?=)
Date: Mon, 27 Jul 2015 09:33:34 +0300
Subject: IcedTea8
In-Reply-To: <55B5CB8D.1080002@jajcus.net>
References: <55B52D72.4040101@pld-linux.org> <55B5CB8D.1080002@jajcus.net>
Message-ID: <55B5D0BE.8000304@pld-linux.org>

On 27.07.2015 09:11, Jacek Konieczny wrote:
> And probably it might be a better idea to build OpenJDK directly 
> instead of using IcedTea8. Current OpenJDK should be buildable on its 
> own, though probably without x32 support. 

didn't even know OpenJDK and IcedTea are different things :)

-- 
glen



From glen at pld-linux.org  Mon Jul 27 08:35:53 2015
From: glen at pld-linux.org (=?UTF-8?B?RWxhbiBSdXVzYW3DpGU=?=)
Date: Mon, 27 Jul 2015 09:35:53 +0300
Subject: IcedTea8
In-Reply-To: <55B5CB8D.1080002@jajcus.net>
References: <55B52D72.4040101@pld-linux.org> <55B5CB8D.1080002@jajcus.net>
Message-ID: <55B5D149.6090809@pld-linux.org>

On 27.07.2015 09:11, Jacek Konieczny wrote:
> And probably it might be a better idea to build OpenJDK directly 
> instead of using IcedTea8. Current OpenJDK should be buildable on its 
> own, though probably without x32 support. 

how would pld name the package?

a) openjdk.spec?
b) openjdk8.spec?

in Fedora it's like this:

[~/fc] ? cat java-1.7.0-icedtea/dead.package; echo
java-1.7.0-icedtea was replaced by java-1.6.0-openjdk.

[~/fc] ? LC_ALL=C ls -ld *openjdk*
drwxr-xr-x 3 glen users 36 May 9 2012 java-1.6.0-openjdk/
drwxr-xr-x 3 glen users 36 Jul 12 2014 java-1.7.0-openjdk/
drwxrwxr-x 3 glen users 4096 Jul 22 08:01 java-1.8.0-openjdk/

[~/fc] ?


-- 
glen



From jajcus at jajcus.net  Mon Jul 27 08:43:32 2015
From: jajcus at jajcus.net (Jacek Konieczny)
Date: Mon, 27 Jul 2015 08:43:32 +0200
Subject: IcedTea8
In-Reply-To: <55B5D149.6090809@pld-linux.org>
References: <55B52D72.4040101@pld-linux.org> <55B5CB8D.1080002@jajcus.net>
 <55B5D149.6090809@pld-linux.org>
Message-ID: <55B5D314.7080904@jajcus.net>

On 2015-07-27 08:35, Elan Ruusam?e wrote:
> On 27.07.2015 09:11, Jacek Konieczny wrote:
>> And probably it might be a better idea to build OpenJDK directly
>> instead of using IcedTea8. Current OpenJDK should be buildable on its
>> own, though probably without x32 support.
>
> how would pld name the package?
>
> a) openjdk.spec?
> b) openjdk8.spec?

b) openjdk8.spec

That works well in any intermediate stages and worked well for sun-java* 
and icedtea*.

> in Fedora it's like this:
>
> [~/fc] ? cat java-1.7.0-icedtea/dead.package; echo
> java-1.7.0-icedtea was replaced by java-1.6.0-openjdk.

That is clearly different from our current scheme, which works quite 
well for us.

Jacek


From glen at pld-linux.org  Mon Jul 27 08:47:55 2015
From: glen at pld-linux.org (=?UTF-8?B?RWxhbiBSdXVzYW3DpGU=?=)
Date: Mon, 27 Jul 2015 09:47:55 +0300
Subject: IcedTea8
In-Reply-To: <55B5D314.7080904@jajcus.net>
References: <55B52D72.4040101@pld-linux.org> <55B5CB8D.1080002@jajcus.net>
 <55B5D149.6090809@pld-linux.org> <55B5D314.7080904@jajcus.net>
Message-ID: <55B5D41B.2020308@pld-linux.org>

On 27.07.2015 09:43, Jacek Konieczny wrote:
>> how would pld name the package?
>>
>> a) openjdk.spec?
>> b) openjdk8.spec?
>
> b) openjdk8.spec
>
> That works well in any intermediate stages and worked well for 
> sun-java* and icedtea*.

there's openjdk.spec already. what to do with it?

https://github.com/pld-linux/openjdk/commits/master

-- 
glen



From jajcus at jajcus.net  Mon Jul 27 10:12:22 2015
From: jajcus at jajcus.net (Jacek Konieczny)
Date: Mon, 27 Jul 2015 10:12:22 +0200
Subject: IcedTea8
In-Reply-To: <55B5D41B.2020308@pld-linux.org>
References: <55B52D72.4040101@pld-linux.org> <55B5CB8D.1080002@jajcus.net>
 <55B5D149.6090809@pld-linux.org> <55B5D314.7080904@jajcus.net>
 <55B5D41B.2020308@pld-linux.org>
Message-ID: <55B5E7E6.70403@jajcus.net>

On 2015-07-27 08:47, Elan Ruusam?e wrote:
> On 27.07.2015 09:43, Jacek Konieczny wrote:
>>> how would pld name the package?
>>>
>>> a) openjdk.spec?
>>> b) openjdk8.spec?
>>
>> b) openjdk8.spec
>>
>> That works well in any intermediate stages and worked well for
>> sun-java* and icedtea*.
>
> there's openjdk.spec already. what to do with it?
>
> https://github.com/pld-linux/openjdk/commits/master
>

It is from 2011? Looks like early Java 7, which never worked. I guess
you can start from scratch with openjdk8.spec.

Jacek


From ed at yen.ipipan.waw.pl  Mon Jul 27 12:29:25 2015
From: ed at yen.ipipan.waw.pl (=?utf-8?B?xYF1a2FzeiBNYcWba28=?=)
Date: Mon, 27 Jul 2015 12:29:25 +0200
Subject: IcedTea8
In-Reply-To: <55B5CB8D.1080002@jajcus.net>
References: <55B52D72.4040101@pld-linux.org> <55B5CB8D.1080002@jajcus.net>
Message-ID: <2540323.n8zxM9cX6P@laptok>

Dnia poniedzia?ek, 27 lipca 2015 08:11:25 Jacek Konieczny pisze:
[...]
> And probably it might be a better idea to build OpenJDK directly instead
> of using IcedTea8. Current OpenJDK should be buildable on its own,
> though probably without x32 support.

Just to make sure, if I get it right - does it mean, that if noone takes care 
of IcedTea8, we'll end up without Java8 for i686?
-- 
?ukasz Ma?ko                                                            _o)
Lukasz.Masko(at)ipipan.waw.pl                                           /\\
Registered Linux User #61028                                           _\_V
Ubuntu: staroafryka?skie s?owo oznaczaj?ce "Nie umiem zainstalowa? Debiana"



From jajcus at jajcus.net  Mon Jul 27 12:33:47 2015
From: jajcus at jajcus.net (Jacek Konieczny)
Date: Mon, 27 Jul 2015 12:33:47 +0200
Subject: IcedTea8
In-Reply-To: <2540323.n8zxM9cX6P@laptok>
References: <55B52D72.4040101@pld-linux.org> <55B5CB8D.1080002@jajcus.net>
 <2540323.n8zxM9cX6P@laptok>
Message-ID: <55B6090B.90706@jajcus.net>

On 2015-07-27 12:29, ?ukasz Ma?ko wrote:
> Dnia poniedzia?ek, 27 lipca 2015 08:11:25 Jacek Konieczny pisze:
> [...]
>> And probably it might be a better idea to build OpenJDK directly instead
>> of using IcedTea8. Current OpenJDK should be buildable on its own,
>> though probably without x32 support.
>
> Just to make sure, if I get it right - does it mean, that if noone takes care
> of IcedTea8, we'll end up without Java8 for i686?

i686 is supported, x32 is not. x32 is something else (32 bit code for 
x86-64 platform running 64-bit kernel).

OpenJDK is the upstream source code, mostly identical to the one from 
which Oracle Java is built. IcedTea8 includes some goodies on top of 
that including alternative virtual machine implementations which can run 
on platforms not supported upstream. We used that for i486 and use it 
for x32 now.

There is also a possibility that current OpenJDK can support those 
platforms ? I am not sure about that.

Jacek