Eric Spakman wrote: >Natanael, > > >>>No the problem is not with initial building packages but save the >>>config changes in a running system. Because it all runs in RAM changes >>>would get lost when you reboot or halt the system. So changes needs to >>>get back-upped in the package. That's why we use both list and >>>exclude.list files. >>> >>> >>Ah, ok... >> >>I have been thinking of package overlays with the local >>config/modifications. The original packages are never overwritten. >>Instead I use a .backup meta file of all files that should be backed up. >>During boot, the runtime apks are first loaded, then will apk overlays >>be installed. >> >>So only modifications are stored. >> >>The backup list should only contain files and no directories to avoid >>backing up temp files etc. >> >> >> > >That only partial solves the problem, some programs also need some specific >empty directories to be available where temporary data is saved. Some examples >are shorewall, openswan, root, dnsmasq, dhcpd, .... So those (empty) >directories should be saved in the package, or created somehow. > > Since everything is using plain tar, it is *possible* to include directories in backup lists, apk's. That might be needed in cases you mention.
But there is an alternative. apk_add will look for a pre-install and post-install script among the meta files. Those are executed before and after unpacking the package. Here you could create empty dirs, create users, handle existing configs, etc. -- Natanael Copa ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. Get your fingers limbered up and give it your best shot. 4 great events, 4 opportunities to win big! Highest score wins.NEC IT Guy Games. Play to win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20 _______________________________________________ leaf-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/leaf-devel
