Thanks for your comments, Eric. > An other option is to add the plugins from within webconf itself, with a
> webconf like "leaf.cfg" file. I think for people using webconf, it doesn't > matter where the list is saved. I think it's even easier to hide that layer > for most users. The only reason for leaf.cfg to be on a block device is that > the lrp packages must be loaded with booting, while that isn't necessary for > webconf plugins. So if people disagree this also an option. Ok, that's fine - /etc/webconf/webconf.conf Might as well move the .webconf files there too (more FHS compliant) > > The lwp format can also be used for packages that need to save state (if they > exist), the lwp file is just a tar.gz I suppose? Right. > So a simple addition for > saving lwp files in the webconf package backup system should work. (just to > keep the destinction between packages and plugins) > I guess my thinking is a plugin is loaded from disk, but you never want to "save" it back to disk. The way package management works, if we aren't careful, the <packagename.lwp> could end up being saved in webconf.lrp or (worse) root.lrp. So stuff in a .lwp should only put files in directories that are marked "exclude". webconf.exclude.list would include /etc/webconf/* /var/webconf/* lrpstat.lrp is an example of something that wouldn't be a "lwp" - it adds the /usr/sbin/lrpStat binary. If it were a lwp, then the lrpStat would get backed up with root.lrp. ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
