Currently, we can install packages from github, using the pacman's install, but there's no tracking of where they came from, so there's no support for updating them.
So, I've been thinking about maintaining a GITHUBADDONS_jpacman_ which is structured like ADDONS_jpacman_ (five columns: FOLDER, VERSION, depends, CAPTION, DESCRIPTION). These five columns all would come from the package's manifest.ijs (except that depends would be (;(,',',])each/cutLF DEPENDS) because DEPENDS is newline delimited and we want commas for ADDONS). And, either install_gitrepo_jpacman_ or readpackage_jpacman_ (or perhaps some other routine) would ensure that the manifest contents were stored in this GITHUBADDONS which, in turn, would be stored some place like ~/user/config/github-addons.txt That's step 1. Step 2 would be to add UI support for updating these addons. I guess, for this, we would need to re-download each manifest for each installed github addon, and we'd want a (perhaps optional) 'github' tab in the pacman ui, listing these addons. Later on, we might want an official prebuilt github-addons.txt and only store in the user's config the entries absent from that. But that would be more of an obstacle than a help, for step 2. But before I get too carried away here... how does this sound? Am I overlooking critical issues? Thanks, -- Raul ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
