From: Richard Leitner <richard.leitner@skidata.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-java][PATCH 4/4] openjdk-8: add recipes for openjdk-8 and openjre-8
Date: Thu, 29 Oct 2015 16:49:26 +0100 [thread overview]
Message-ID: <56324006.8040905@skidata.com> (raw)
In-Reply-To: <CAP9ODKoUv+-WXzXNEKdFWwFDbJnQGXZtiZzqXtBzS7MmwOXkYA@mail.gmail.com>
On 10/29/2015 01:24 PM, Otavio Salvador wrote:
> On Thu, Oct 29, 2015 at 9:54 AM, Richard Leitner
> <richard.leitner@skidata.com> wrote:
>> On 10/29/2015 12:24 PM, Jens Rehsack wrote:
>>>
>>>> Am 29.10.2015 um 11:46 schrieb Otavio Salvador <otavio.salvador@ossystems.com.br>:
>>>>
>>>> On Thu, Oct 29, 2015 at 7:22 AM, Jens Rehsack <rehsack@gmail.com> wrote:
>>>>>> Am 29.10.2015 um 08:41 schrieb Richard Leitner <richard.leitner@skidata.com>:
>>>>>> To cite Otavio:
>>>>>> We could rename the patches directory for openjdk-7 and avoid the
>>>>>> version number on it. This would make easier for upgrades and to see
>>>>>> the diff between the patches.
>>>>>
>>>>> So git diff -M doesn't work for you? I don't understand the reasoning.
>>>>
>>>> It does but reusing the directory easy the upgrade and as the
>>>> openjdk-8 is in maintenance it is expected that it does not change
>>>> much in the patches.
>>>
>>> Partial. As I told you, I updated OpenJDK from 8u40 to 8u72 when I first
>>> encountered massive crashes on the target device with zeroshark until
>>> llvm guys told me, that legacy JIT for ARM was utterly broken and they
>>> force people to MCJIT.
>>>
>>> Having both directories during the upgrade helped me massively to
>>> avoid breaking patches by fixing against new upstream adoptions.
>>>
>>> Surely, this could be handled developer-side by keeping an foo.old
>>> directory - but it smells the same smell ;)
>>>
>>> I don't fight against renaming the directory, I just argue, both
>>> way have their own kind of smell.
>>>
>>
>> I really understand both sides... But for me, due to the fact we want to
>> support only one version of each OpenJDK release, the patch directory
>> without version has "a better smell" ;-)
>>
>> I would also go one step further and omit the version from
>> openjdk-7-release-*.inc. Then the version number is only included in the
>> name of the openjdk-7_*.bb file.
>>
>> But I'm open to any discussion! So what do you think about it?
>
> I agree; and if we possible fix the indenting and reduce the
> indirection (reducing the number .inc files, for example) I would
> support :-D
>
Ok, i will prepare a patch for fixing the filenames in openjdk-7.
What indentation should be chosen? Tabs? Spaces (how much)?
Maybe I have also time to fix that in the recipes-core.
best regards;
Richard L
next prev parent reply other threads:[~2015-10-29 15:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-28 18:01 [meta-java][PATCH 4/4] openjdk-8: add recipes for openjdk-8 and openjre-8 Jens Rehsack
2015-10-28 19:34 ` Dan McGregor
2015-10-28 19:59 ` Jens Rehsack
2015-10-29 7:41 ` Richard Leitner
2015-10-29 9:22 ` Jens Rehsack
2015-10-29 10:46 ` Otavio Salvador
2015-10-29 11:24 ` Jens Rehsack
2015-10-29 11:54 ` Richard Leitner
2015-10-29 12:08 ` Jens Rehsack
2015-10-29 15:51 ` Richard Leitner
2015-10-29 12:24 ` Otavio Salvador
2015-10-29 15:49 ` Richard Leitner [this message]
2015-10-29 16:03 ` Otavio Salvador
2015-10-29 18:51 ` Richard Leitner
2015-10-29 18:59 ` Otavio Salvador
2015-11-03 10:25 ` Jens Rehsack
-- strict thread matches above, loose matches on Subject: below --
2015-10-27 20:31 Jens Rehsack
2015-10-30 9:09 ` Kaaria, Erkka
2015-10-30 11:46 ` Jens Rehsack
2015-10-30 12:41 ` Kaaria, Erkka
2015-10-30 12:59 ` Otavio Salvador
2015-10-30 13:26 ` Jens Rehsack
2015-10-30 13:23 ` Jens Rehsack
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56324006.8040905@skidata.com \
--to=richard.leitner@skidata.com \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.