Skip to content

strategy merge behaves confusingly #63

@HumpityDumpityDumber

Description

@HumpityDumpityDumber

I have my waybar configuration set up with matugen so matugen creates a colors.css in ~/.config/waybar/

Because of this I don't want the waybar folder to be symlinked but instead whatever files are in it to be symlinked instead. My issue is that if i use strategy merge on ~/.config/waybar/ it only does what i want if the waybar folder already exists, but if ~/.config/waybar/ doesn't exist it just symlinks the entire waybar egg over and then matugen starts putting the colors.css into my yolk egg. Is there any particular way to fix this problem that I haven't come across? I thought strategy merge would work but with its inconsistant behavior it's not ideal.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions