Package Details: geant4 11.3.0-1

Git Clone URL: https://aur.archlinux.org/geant4.git (read-only, click to copy)
Package Base: geant4
Description: A simulation toolkit for particle physics interactions.
Upstream URL: http://geant4.cern.ch/
Keywords: matter montecarlo radiation transport
Licenses: custom: http://geant4.cern.ch/license/
Conflicts: geant4_devel
Submitter: Eothred
Maintainer: donpicoro
Last Packager: donpicoro
Votes: 19
Popularity: 0.000099
First Submitted: 2010-04-08 08:54 (UTC)
Last Updated: 2024-12-08 19:13 (UTC)

Dependencies (29)

Sources (2)

Latest Comments

« First ‹ Previous 1 .. 9 10 11 12 13 14 15 Next › Last »

Eothred commented on 2010-09-02 17:32 (UTC)

Oops, my bad. Fixed now. Thanks!

<deleted-account> commented on 2010-09-02 17:26 (UTC)

I think there is a mistake in the "arch" line of the PKGBUILD. Instead of i386 it should be i686. After changing it, I could install the package.

Eothred commented on 2010-09-02 17:25 (UTC)

Good question. I thought so? Perhaps it is only needed during compilation. At the moment I basically set the same dependencies as I have in the debian package which I adopted by a more skilled packager than me. I can have a look more in detail. If anyone can confirm the dependency one way or the other please inform me in the comments here. I would not be surprised if this package has issues in certain modules. I am not a heavy user myself, so I have not tested it as thorough as I would've liked (I also have a PhD to write so my spare time is not limitless ;) ). General testing is most welcome!

<deleted-account> commented on 2010-09-02 16:28 (UTC)

Hello thanks for the packages. I am also using Geant4 at work and will give the packages a try. Hopefully saves some time . :) If you need help with anything feel free to contact me. I am willing to contribute. Btw. I had it installed without cernlib. Is it really necessary as dependency?

Eothred commented on 2010-07-13 11:26 (UTC)

OK, thank you very much for your information. I see that there is another package called DAWN in AUR, which I added as optional dependency. http://aur.archlinux.org/packages.php?ID=26848 A few things you can help me with: -Extend the line "optdepends" in the PKGBUILD file and post the changes here or send them to me. OpenGL is already defined as a dependency (libgl), I couldn't find JAS or wired3 in the Arch build system or in AUR (they might have a different name). -Test the packages, and report any problems. The debian build is based on a few patches (not written by me), and requires an automated build script. I will see what I can do about heprep (it isn't included in the current version?)

donpicoro commented on 2010-07-12 19:27 (UTC)

When you create your geometries, you can view them using many drivers as they call them. Different drivers work for different purposes. The HepRep is probably the preferred one when you are developing your geometry because it allows you to rotate it, zoom and and the like. But if you want to show your already constructed geometry, let's say in a conference, it is better to use another: for example DAWN. DAWN renders very nicely ghostscripts (.ps) files -hence the gv dependence- with textures and shadows... and if you use it properly in conjunction with the 'david' software you can find non trivial overlaps in your geometry. Maybe I did not use the correct word... it is not 'additional dependencies'. What I wanted to say was 'optional dependencies'. There are many more optional dependencies (openGL, wired3, JAS, root, etc), I just wanted to point out the fact that it will be nice to include some of the 'visualization' dependencies.

Eothred commented on 2010-07-11 08:57 (UTC)

Cleaned the PKGBUILD as requested. What is dawn and gv required for? I am not using geant4 extensively myself, so I do not actually know the code very well. I'll be happy to add them as dependencies if they are needed for the "full experience".

Eothred commented on 2010-07-11 08:49 (UTC)

I use the debian package because it is easy for me (I am anyway maintaining the debian packages as well), and it pre-build installs much quicker (geant4 compilation is easily a couple of hours). I guess in principle this package should be named geant4-deb or something, and then another person could take care of creating a PKGBUILD which directly installs from source. In addition, this debian package uses some wrapper scripts so that you don't have to mess up your environment with all the geant4-variables. Yes, I solved the clhep issue. Temporary fixes are commented out, but should remove them completely as you say. I just wanted to wait until this version was confirmed working.

donpicoro commented on 2010-07-08 20:26 (UTC)

WOW this is an interesting package... I would love to do something about it. How can I help? did you already solved the clhep issues? according to you last post it seems like it, but then I suggest you to have a clean PKGBUILD file... or explain a little bit more those temporary fixes. Why do we have to rely on the debian package?... I have geant4 up an running with my arch installation with no problems at all. How about adding dawn and gv as additional dependencies. I do not how, but I am willing to learn how to create maybe the wired and HepRApp packages. What do you think? Thanks !!!

Eothred commented on 2010-05-11 15:13 (UTC)

Sorry for my delay (too much to do at work these days..). The updated geant version is linked against clhep 2.0.4.6, and clhep in aur has updated package version. I checked 64bit and it seems to work fine. If someone could check 32bit version and comment here how it went, I'd be happy :)

« First ‹ Previous 1 .. 9 10 11 12 13 14 15 Next › Last »