dravenloft
Joined: 15 Nov 2006
Posts: 1
Location: Augusta, Ga
|
 Posted: Wed Nov 15, 2006 1:59 pm Post subject: Installing packages not part of the moonbase |
 |
|
I am not unfamiliar with installing from source, but I was wondering about doing it with this system where things are actually designed for doing that.
Namely how I could ensure that the optimisations and directory structures I have configured for the software that comes with lunar get applied to the software I download from sourceforge or wherever.
Also how I might uninstall it afterward, if there's a way for the lin and lrm to track the package, etc... |
|
engelsman
Joined: 21 Aug 2005
Posts: 131
Location: Netherlands
|
| Posted: Wed Nov 15, 2006 2:46 pm Post subject: Overview of the Lunar Package Management system |
|
|
The great strength of Lunar is its package management system, and if you want to avoid problems in the future, you should really work within the package management system rather than just downloading source, unpacking, running configure and then make install. The Lunar package management system will do that for you, but you have to play by its rules. If you do, you can install and uninstall using lin and lrm.
The package management system is built around the moonbase. The moonbase is divided into logical sections and in each section there are a number of directories, each representing a module. Each module directory contains files used by the package management system. The minimum configuration consists of just a DETAILS file which defines module name, version, download path, website, etc. If a module requires other packages to be installed first, these will be mentioned in a DEPENDS file. If the package requires the default build process to be customised in some way, there will be a BUILD file.
If you want to develop your own local modules, you will need to tell the package management system to look in the zlocal section of the moonbase, either by running the lunar command, going to the Options menu, the Features sub-menu and then setting ZLOCAL_OVERRIDES on, or doing it directly from the command line: | Code: | | lunar set ZLOCAL_OVERRIDES on |
If you want to modify or update an existing module, you will need to set ZLOCAL_OVERRIDES on as above, and then run to copy the DETAILS and other files into zlocal/module. You can then edit this local copy without losing any work next time you update the main moonbase.
Of course, in the spirit of open source cooperation, you will want to share your new module or updates with the rest of the Lunar community. To do this you will need to be subscribed to the lunar mailing list, and have an outgoing mail program installed. The simplest is esmtp. Then all you need to do is fill in the pre-formatted form presented to you after typing
Further details about building modules can be found under the Documentation pages. |
|
FAQ
Search
Memberlist
Usergroups
Profile
Log in to check your private messages
Log in
