Skip to content

Inconsistent ordering of dependency constraints in Puppetfile.lock #71

Description

@benpillet

Sometimes librarian-puppet install will update the Puppetfile.lock with the constraint in a different order than the original Puppetfile.lock.
e.g.
before:

...
puppet-archive (1.3.0)
    puppetlabs-stdlib (>= 4.6.0, < 5.0.0)
...

after:

...
puppet-archive (1.3.0)
    puppetlabs-stdlib (< 5.0.0, >= 4.6.0)
...

There's no logical difference in the dependency, but when the ordering changes, the diff changes and makes for git commit's that are long with many lines changing that obscure actual changes.

This may be an issue in librarianp, not librarian-puppet, but it I'm opening this to start the digging.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions