Hi Ludo' ,
First of all thank you for putting the time for working on this, I hope we are close to a solution :)
I think we’ll only want to support two layouts: Stow and “plain”; we should avoid overengineering that. That’s why a simple (layout 'stow) field seems good enough for me. WDYT?
I think it is important, if the effort is feasible, to not leave
anyone behind (in terms of what the features of this service are)
. Having a single field without further changes will introduce
some ambiguity imo. We have these requirements in my
understanding:
Also since I first sent this service around Jan 2023 (when it was still the home-stow-migration-service), and it has been broken on master for some time I'd like to provide a fix for this situation as soon as possible (clearly the definition of brokennes and what changes to the API would be breaking user configs depends on the requirements one intends for the home-dotfiles-service-type, especially since the changes that broke master were introduced without consensus).
I'm changing the code to: use the layout field, support Stow's users workflow adding a new optional field called packages, which makes sense only if the layout is 'stow, and I'm making the directories field a string instead of a list of strings. Please let me know your thoughts on this v3.
Thank your for your work,
giacomo