Hi, the following cannot be performed in a series if 'foo' was the only (read last) overlay installed or when user just installed layman for the first time on a particular host and knows from top of his head what he/she want to install: layman -d foo; layman -a foo It seems 'layman -L' precreates the necessary directory structure and obtain soem XML listing of repositories. Personally I would have preferred if 'layman -a foo' eventually called on its ow 'layman -L' if that was needed. Currently I have to do depending on the situation one of these two: new host# layman -L; layman -a foo reinstall# layman -d foo; layman -L; layman -a foo
Here is the list of actions that automatically run a "layman -f": # Actions that implicitly call the fetch operation before fetch_actions = ['sync', 'sync_all', 'list'] It has always been that you must do a -f,--fetch or -L before adding overlays. As without the list, it has no reference data to use to know how to install the overlay. Also, doing a fetch always before an add could be an unwanted behavior. Especially if someone is in the process of changing links and needing to test the changes before submitting them to be updated in the repositories.xml list.
