From: Steve L. (JIRA) <ji...@sm...> - 2008-11-17 17:32:04
|
[ http://jira.smartfrog.org/jira/browse/SFOS-1030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11365#action_11365 ] Steve Loughran commented on SFOS-1030: -------------------------------------- 1. The items inside would be conditional. 2. You'd have an RpmPackage that would represent a package within the spec file, with name, covering text, dependencies It would also have scripts to run before/after 3. You'd also have items that would exist within a package: files, directories and symlinks {code} AbstractRpmFile extends Prim { user; group; permissions; path TBD; } RpmFile extends AbstractRpmFile { } RpmDirAbstractRpmFile { } RpmSymLink extends AbstractRpmFile { } {code} When the various items are deployed, they set up the filesystem and add the relevant declaration to their owning RPM Package; that would have to be something to build up a list of participants that it would ask for setup, .spec teardown and validation parameters, params that would go into the .spec file. > Add components to build an RPM .spec file with corresponding files > ------------------------------------------------------------------ > > Key: SFOS-1030 > URL: http://jira.smartfrog.org/jira/browse/SFOS-1030 > Project: SmartFrog > Issue Type: New Feature > Components: _service_rpm > Affects Versions: 3.15.x > Reporter: Steve Loughran > Assignee: Steve Loughran > Fix For: 3.15.x > > > Rather than have a separate .spec file that needs manipulating, and lots of components to set up the directories first, why not merge them into SmartFrog components that can set up the RPM directories and generate a corresponding .spec file -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.smartfrog.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |