Bug #4316
closedre-evaluate how kars are managed in the build and runtime
0%
Description
Currently modules have a /resources/kar directory containing a folder corresponding to each kar. This folder is checked in to SVN. Then whenever we start kepler we "Build Kars" and the /resources/kar/<karName> directory gets turned into a kar file in the /kar directory. Which Kepler then immediately unpacks again and starts using.
We should remove the resources/kar directory from svn and check in the kar files themselves. Then create a build target that will unpack the kars to the /resources/kar directory when desired (svn.ignore should be set on the /resources/kar directory to make sure it does not get checked into svn).
Another target would create a new directory in /resources/kar with a skeleton actor for people who want to create a new kar. And another target would build a kar file in the /kar directory from the files in a /resources/kar/<karName> directory and roll the LSID revision each time the kar is built.
This enhancement will reduce checkout time and startup time and provide an automated mechanism for updating KAR revisions.
Related issues
Updated by Chad Berkley over 15 years ago
Several people do not think that kars should be checked into SVN so there needs to be a discussion amongst stake holders before this is implemented.
Updated by Bertram Ludaescher over 15 years ago
Can someone post here a link to any further documentation about how the "KAR system" is supposed to work? Then we could try and agree on the goals first, then nail down the how-to. Just my $0.02 ;)
Bertram
Updated by Chad Berkley almost 15 years ago
KARs will not be checked into SVN for the forseable future. Closing this bug. We can reopen it at a later time if that becomes necessary.