Skip to content

Package Relocation Commits #54

@luke-patchblox

Description

@luke-patchblox

Hi,

I want to start off by saying that the tool you have built is fantastic and your work on it is very much appreciated.

I was looking at the changes that are being published to standardize certain packages' folder structures and think that the new folder structure is a great design. However, I noticed that it appears that as part of the restructuring, you are deleting the old versions in a particular commit and then later adding them back in the new folder structure in a separate commit.

Because winget's publishing pipeline has a latency in committing these changes, it is highly possible that packages are no longer available until the commits for adding back the packages has been approved. Meaning, winget's package detection will be unable to recognize a package in that time span.

Would it be possible to make the changes in a single commit? In other words, both the old package deletion and package addition are done in a single commit therefore eliminating the timespan in which a package is entirely eliminated from the manifests. Or is there an inherent limitation with doing this due to their automation pipeline?

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