Am 18.09.18 um 00:23 schrieb Carsten Mattner via arch-general:
> Hope you don't mind me hijacking the thread to ask if you've ever
> extracted an adoptopenjdk tarball and were able to use it for running
> a Swing GUI. The jdk10-openjdk (not bin, didn't try aur) package in arch
> works, but
A non-Arch specific alternative would be to use sdkman: https://sdkman.io/
, which is a generic version/environment manager for JVM-related packages.
I've used it when I wanted to install some SDKs that wouldn't clobber the
system-installed ones.
On Mon, Sep 17, 2018 at 9:34 AM Peter Nabbefeld
On 9/17/18, Guus Snijders via arch-general wrote:
> As an alternative : you could just extract (unpack) the pkg file to a
> versioned directory in your $home and use those for testing.
Hope you don't mind me hijacking the thread to ask if you've ever
extracted an adoptopenjdk tarball and were
Op ma 17 sep. 2018 18:34 schreef Peter Nabbefeld :
>
>
> [...]
>
> Yes and No. These tools allow switching the active JVM. In my case that
> would be overkill, I don't need that. I only need the installed software
> to be reachable from NetBeans IDE. I'm usually fine running my software
> on the
On 9/17/18 6:27 PM, Doug Newgard via arch-general wrote:
>
> Going forward with the new release policies, would it be better to just have
> an
> openjdk/openjre package that's always the latest version, then versioned
> packages for the lts releases, such as they are?
>
This is exactly what
On Mon, Sep 17, 2018 at 6:34 PM Peter Nabbefeld wrote:
>
>
>
> Am 17.09.18 um 17:48 schrieb Carsten Mattner via arch-general:
> > On 9/17/18, Eli Schwartz via arch-general
> > wrote:
> >
> >> So essentially what you really want is a way for pacman to remember your
> >> choice. That would
Am 17.09.18 um 17:48 schrieb Carsten Mattner via arch-general:
On 9/17/18, Eli Schwartz via arch-general wrote:
So essentially what you really want is a way for pacman to remember your
choice. That would require pacman modify its configuration which is
something that goes against the
Am 17.09.18 um 16:21 schrieb Eli Schwartz via arch-general:
On September 17, 2018 10:06:04 AM EDT, Peter Nabbefeld
wrote:
You will get prompted again and again on every pacman -Su "to see if
you're finally ready to do the replacement".
That's what I don't want - if I accidently don't
On Mon, 17 Sep 2018 18:20:49 +0200
Guillaume ALAUX via arch-general wrote:
> On Mon, Sep 17, 2018 at 5:48 PM Carsten Mattner via arch-general
> wrote:
> >
> > On 9/17/18, Eli Schwartz via arch-general
> > wrote:
> >
> > > So essentially what you really want is a way for pacman to remember
Am 17.09.18 um 18:20 schrieb Guillaume ALAUX via arch-general:
> On Mon, Sep 17, 2018 at 5:48 PM Carsten Mattner via arch-general
> wrote:
>> On 9/17/18, Eli Schwartz via arch-general wrote:
>>
>>> So essentially what you really want is a way for pacman to remember your
>>> choice. That would
On Mon, Sep 17, 2018 at 5:48 PM Carsten Mattner via arch-general
wrote:
>
> On 9/17/18, Eli Schwartz via arch-general wrote:
>
> > So essentially what you really want is a way for pacman to remember your
> > choice. That would require pacman modify its configuration which is
> > something that
On 9/17/18, Eli Schwartz via arch-general wrote:
> So essentially what you really want is a way for pacman to remember your
> choice. That would require pacman modify its configuration which is
> something that goes against the current architecture... What would happen
> instead is pacman.conf
On September 17, 2018 10:06:04 AM EDT, Peter Nabbefeld
wrote:
>> You will get prompted again and again on every pacman -Su "to see if
>> you're finally ready to do the replacement".
>>
>That's what I don't want - if I accidently don't type the "n" for some
>reason, the JDK will be raplaced.
Am 17.09.18 um 15:58 schrieb Eli Schwartz via arch-general:
On 9/17/18 7:50 AM, Peter Nabbefeld wrote:
Sorry, I accidently sent my earlier response to Olli privately. So one
question has been lost:
Probably, pacman could be extended with an option to change the update
strategy from replace
On 9/17/18 7:50 AM, Peter Nabbefeld wrote:
> Sorry, I accidently sent my earlier response to Olli privately. So one
> question has been lost:
>
> Probably, pacman could be extended with an option to change the update
> strategy from replace to add?
>
> This would make it a lot easier than
It seems like some recent package installation or upgrade has been breaking my
Lxde desktop. The taskbar at the bottom of the screen keeps freezing up
periodically - doesn't repaint (except for non-lxde icons like network manager
applet), doesn't respond to mouse clicks, etc. Then after a few
Am 17.09.18 um 12:42 schrieb Luke English:
On Mon, Sep 17, 2018 at 12:34:54PM +0200, Guus Snijders via arch-general wrote:
Op ma 17 sep. 2018 12:04 schreef Olli :
On 17.09.18 09:31, Peter Nabbefeld wrote:
There has ever been an EOL for older JDKs. But sometimes You're bound
to a specific
On Mon, Sep 17, 2018 at 12:34:54PM +0200, Guus Snijders via arch-general wrote:
> Op ma 17 sep. 2018 12:04 schreef Olli :
>
> > On 17.09.18 09:31, Peter Nabbefeld wrote:
> > > There has ever been an EOL for older JDKs. But sometimes You're bound
> > > to a specific JDK version in Your working
Op ma 17 sep. 2018 12:04 schreef Olli :
> On 17.09.18 09:31, Peter Nabbefeld wrote:
> > There has ever been an EOL for older JDKs. But sometimes You're bound
> > to a specific JDK version in Your working environment, so IMO always
> > replacing is a bad strategy. The problem is, in larger
On 17.09.18 09:31, Peter Nabbefeld wrote:
> There has ever been an EOL for older JDKs. But sometimes You're bound
> to a specific JDK version in Your working environment, so IMO always
> replacing is a bad strategy. The problem is, in larger companies it
> sometimes takes some weeks or even months
20 matches
Mail list logo
