Chakra is an off-shoot of Arch, so once we get this package ready it should be a small matter to prepare the same for Arch and other Arch derivatives.
i assume that every dependency that is not already in CCR or Chakra repos needs a pkgbuild constructed and to be built from source. i asked for help in this thread on the forum:
So the questionable dependancies in which I haven't found the source code to are: db4o (its open source so they must provide the source somewhere) & swing app framework - I just used the jars from netbeans so I will need to find where this is from which I am assuming its Oracle.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
db4o seems to be in the chakra community repos (CCR) already. version 8.0-1.
as for swing app, is that the filename? here's what we have in ccr for swing
[nicodemus@Naiad ~]$ ccr swing
0 ccr/java-flexdock 1.1.1-2
Docking framework for Swing
1 ccr/java-skinlf 6.7-3
Skinning engine for Swing
2 ccr/jrosetta 1.0.4-2
Graphical console engine for Swing
3 ccr/hammerfight 1.004-1 [Humble Bundle 3&4] A 2D physics-based video game in which you swing large melee weapons
to destroy enemies
4 ccr/jgoodies-looks 2.4.2-1
A Java Swing look and feel library
5 ccr/joxy-git 20130218-1
Java Swing Look and Feel for integration with the KDE Oxygen theme.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ah, so it seems that the CCR is pulling the minecraft jar. I think it would be much easier to just do this, making the jar files available that are necessary.
So it might be easier for me to just provide the jnostromo.jar - what do you think? It also might be easier to just download the jars (like in minecraft) than having to build from source...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
life is getting busy for me, but this remains on my mind.
note that i'm moving away from Chakra for the time being and am instead playing around with Manjaro. it's another Arch derivative, but it uses the Arch User Repo just like Arch does, as do most other Arch-based distros except Chakra.
doing the package build for the AUR first will let us hit the most distros fastest, and it is then an easy matter to convert that for Chakra's CCR.
1) git clone https://conzar@git.code.sf.net/p/jnostromo/code jnostromo-code
2) list below
* db4o - db4o-8.0.236.16058-core-jara5.jar http://www.db4o.com/downloads/db4o-8.0-java.zip
* jinput - latest https://github.com/sgothel/jinput.git
* itextpdf - itextpdf-5.2.1.jar https://sourceforge.net/p/itext/code/HEAD/tree/ or jar http://sourceforge.net/projects/itext/files/iText/iText5.4.0/itext-5.4.0.zip/download
* swing app framework - appframework-1.0.3.jar & swing-worker-1.1.jar
3) I build it using netbeans so I will need to look at the ant build script.
consolidating info from KBmaster ticket to this project to reduce cross-posting.
great, thanks for this. i'll be working on putting this together, with your help.
here's a link to the packaging standards for Chakra Linux, my distro.
http://chakra-project.org/wiki/index.php?title=Packaging_Standards
Chakra is an off-shoot of Arch, so once we get this package ready it should be a small matter to prepare the same for Arch and other Arch derivatives.
i assume that every dependency that is not already in CCR or Chakra repos needs a pkgbuild constructed and to be built from source. i asked for help in this thread on the forum:
http://chakra-project.org/bbs/viewtopic.php?pid=68866
So the questionable dependancies in which I haven't found the source code to are: db4o (its open source so they must provide the source somewhere) & swing app framework - I just used the jars from netbeans so I will need to find where this is from which I am assuming its Oracle.
db4o seems to be in the chakra community repos (CCR) already. version 8.0-1.
as for swing app, is that the filename? here's what we have in ccr for swing
[nicodemus@Naiad ~]$ ccr swing
0 ccr/java-flexdock 1.1.1-2
Docking framework for Swing
1 ccr/java-skinlf 6.7-3
Skinning engine for Swing
2 ccr/jrosetta 1.0.4-2
Graphical console engine for Swing
3 ccr/hammerfight 1.004-1
[Humble Bundle 3&4] A 2D physics-based video game in which you swing large melee weapons
to destroy enemies
4 ccr/jgoodies-looks 2.4.2-1
A Java Swing look and feel library
5 ccr/joxy-git 20130218-1
Java Swing Look and Feel for integration with the KDE Oxygen theme.
from stevek, a mod at chakra forum:
"A *.jar can be downloaded and then installed in the package() section.
I suggest checking out some other PKGBUILDS for some insight: e.g.http://www.chakra-project.org/ccr/pkgbuild_view.php?p=minecraft
Any additional dependencies not found in the repos or CCR will need to be added to CCR."
Ah, so it seems that the CCR is pulling the minecraft jar. I think it would be much easier to just do this, making the jar files available that are necessary.
So it might be easier for me to just provide the jnostromo.jar - what do you think? It also might be easier to just download the jars (like in minecraft) than having to build from source...
Java App Framework
* appframework-1.03.jar - http://mirrors.ibiblio.org/pub/mirrors/maven2/net/java/dev/appframework/appframework/1.03/appframework-1.03.jar
* swing-worker-1.1.jar - http://mirrors.ibiblio.org/pub/mirrors/maven2/org/swinglabs/swing-worker/1.1/swing-worker-1.1.jar
yeah, that sounds best! i'm still very new to this and trying to get a feel for it. i know they say no binaries, but i'm not sure of the difference.
life is getting busy for me, but this remains on my mind.
note that i'm moving away from Chakra for the time being and am instead playing around with Manjaro. it's another Arch derivative, but it uses the Arch User Repo just like Arch does, as do most other Arch-based distros except Chakra.
doing the package build for the AUR first will let us hit the most distros fastest, and it is then an easy matter to convert that for Chakra's CCR.
Arch packaging standards can be found here:
https://wiki.archlinux.org/index.php/Arch_Packaging_Standards
and a specific wiki entry with standards for Java packages:
https://wiki.archlinux.org/index.php/Java_Package_Guidelines
Last edit: Nicodemus144 2013-04-23
let's close this ticket as KB Master has come far enough now that we can focus our energy on packaging it instead of jnostromo.
Last edit: Nicodemus144 2013-12-11