User avatar
trixon
Posts: 29
Joined: Thu Dec 31, 2015 10:00 pm

Java package guidelines

Wed Jun 28, 2017 9:44 pm

So, while I'm waiting for go/no-go on

https://dev.solus-project.com/T3987
https://dev.solus-project.com/T3986
https://dev.solus-project.com/T3954

I thought I better ask were the best place to store java programs is.
Having done some AUR for my projects I have read guidelines like https://wiki.archlinux.org/index.php/Ja ... _structure

Where would Solus like me to put java "executables" and libraries?

On a side note, why don't we have two openjdk packages, one for the jre and one for the jdk?

User avatar
kyrios
Posts: 1858
Joined: Thu Sep 22, 2016 4:20 pm

Re: Java package guidelines

Thu Jun 29, 2017 8:24 am

trixon wrote:
Wed Jun 28, 2017 9:44 pm
So, while I'm waiting for go/no-go on

https://dev.solus-project.com/T3987
https://dev.solus-project.com/T3986
https://dev.solus-project.com/T3954

I thought I better ask were the best place to store java programs is.
Having done some AUR for my projects I have read guidelines like https://wiki.archlinux.org/index.php/Ja ... _structure

Where would Solus like me to put java "executables" and libraries?

On a side note, why don't we have two openjdk packages, one for the jre and one for the jdk?
I would say under /usr/share. The "executable" should go in /usr/bin (or at least add a symbolic link to the executable there).

Just one thing: Although what you do is really appreciated, you go a little too fast.
First introduce the package request using the template
Then when it's accepted for inclusion, make the package.
You're mixing both and it's quite confusing!

sunnyflunk
Development Team
Posts: 2874
Joined: Sun Mar 13, 2016 11:35 pm

Re: Java package guidelines

Thu Jun 29, 2017 2:10 pm

It should ideally be built from source

User avatar
trixon
Posts: 29
Joined: Thu Dec 31, 2015 10:00 pm

Re: Java package guidelines

Thu Jun 29, 2017 7:23 pm

kyrios wrote:
Thu Jun 29, 2017 8:24 am
I would say under /usr/share. The "executable" should go in /usr/bin (or at least add a symbolic link to the executable there).
Ok, I already have some shell scripts in /usr/bin calling the jar but I could stop using /opt and use something like /usr/share/javaprog/javaprog.jar instead.
kyrios wrote:
Thu Jun 29, 2017 8:24 am
Just one thing: Although what you do is really appreciated, you go a little too fast.
First introduce the package request using the template
Then when it's accepted for inclusion, make the package.
You're mixing both and it's quite confusing!
Sorry about that. While looking at the template I felt that the package file answered all the points in a structured way. :)

User avatar
trixon
Posts: 29
Joined: Thu Dec 31, 2015 10:00 pm

Re: Java package guidelines

Thu Jun 29, 2017 7:26 pm

sunnyflunk wrote:
Thu Jun 29, 2017 2:10 pm
It should ideally be built from source
I understand, there is one or two dependencies that is not available via maven at this time.
Would it be acceptable with a bin-package until it's resolved?

sunnyflunk
Development Team
Posts: 2874
Joined: Sun Mar 13, 2016 11:35 pm

Re: Java package guidelines

Thu Jun 29, 2017 11:53 pm

trixon wrote:
Thu Jun 29, 2017 7:26 pm
sunnyflunk wrote:
Thu Jun 29, 2017 2:10 pm
It should ideally be built from source
I understand, there is one or two dependencies that is not available via maven at this time.
Would it be acceptable with a bin-package until it's resolved?
Typically we would add the deps in (but many java things don't have simple build tools). There are some things in the repo that aren't, but most aren't open source (so can't be). And of course, the real issue is that once you put it in as a binary, it never gets fixed :lol:

Return to “Engagement”