Posted by Sven Gothel on Sep 14, 2011; 2:54am
URL: https://forum.jogamp.org/New-Deployment-FHS-Filesystem-Hierarchy-Standard-tp3334675.html

New Deployment FHS (Filesystem Hierarchy Standard)

See
  [1] http://jogamp.org/deployment/archive/master/gluegen_400-joal_202-jogl_471-jocl_407/

Month ago some of us discussed an easier deployment filesystem layout
in contrast to
  [2] http://jogamp.org/deployment/archive/master/gluegen_306-joal_137-jogl_329-jocl_295/

As you can see, [2] is pretty much spammed with jar files,
and it might not be easy to navigate through it.
Sure, it's not really a humans task to do that .. however.

While elaborating about it, we actually had a few nice ideas:

[a] better sorting of archives (developer files)
[b] creating one big jogamp archive file per platform (like eclipse)

Both is addressed and visible here:
  http://jogamp.org/deployment/archive/master/gluegen_400-joal_202-jogl_471-jocl_407/archive/

(Yes, still using the great 7z compression to save tons of diskspace)

http://jogamp.org/deployment/archive/master/gluegen_400-joal_202-jogl_471-jocl_407/
    archive/
        jogamp-linux-amd64.7z

        jogamp-linux-amd64/
            gluegen-linux-amd64.7z
            jogl-linux-amd64.7z
            ..
            test-results/
                ..

        jogamp-linux-i586.7z
        jogamp-linux-i586/
            ..

        jogl-javadoc.7z
        jogl-demos.7z
        ..

    jar/
        atomic/

    javadoc/
   
    jogl-demos/
        jar/

    log/

Developers have access to both, the original module's 7z platform archive
and the merged jogamp platform archive.

The test results are moved to a local subfolder as well.

The JNLP files are still in there original location,
just updated by the new JAR location in ./jar

I hope this matches how we desired it, ofc we can fix glitches etc.

+++

The root filesystem will change as follows:

http://jogamp.org/deployment/
    v2.0-rc2/
   
    v2.0-rc3/

    jogamp-current/ -> v2.0-rc3

    jogamp-next/ -> archive/rc/gluegen_xx-joal_yy-jogl_zz-jocl_uu-signed


[r1] contains the release version using the release tag version, ie v2.0-rc3
[r2] using symbolic links to allow generic use, ie jogamp-next

Both allows either using the latest or current/stable version
while also using a specified one, ie v2.0-rc2.

The latter maybe a variation for some web application, not willing to update/test
new versions.

+++

Remarks ? Replies ? Critizism ? All is welcome.

Cheers, Sven