-
|
Is there any reason why the PR for adding the package FreeFileSync went stale instead of being processed? I'm asking as I discovered that program today, went to look for it in the repo, didn't find it and thus went looking for an issue or PR mentioning it - before creating an issue to have the package added. I'm not able to create a package template from scratch, let alone come up with patches or to know which files to add. To me the PR looks as if the committer has at least more skills in that regard than me and I wonder why it didn't go through. All I could do is create an issue to ask for the package to be added, but there might be a special reason for why the previous PR was not processed and any package request for FreeFileSync might be denied, too. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
There is most likely no special reasons. Many new packages get stale and don't make through https://github.com/void-linux/void-packages/issues?q=label%3Anew-package%20label%3AStale%20is%3Aclosed%20 Not every new package submitted will get approved. After three months without activity in the corresponding PR, it gets "Stale" automatically. The maintainer can push a new version (or just rebase and force) to remove the "Stale" tag, indicating that they are still active/interested. But it's still not guaranteed for inclusion. |
Beta Was this translation helpful? Give feedback.
There is most likely no special reasons. Many new packages get stale and don't make through https://github.com/void-linux/void-packages/issues?q=label%3Anew-package%20label%3AStale%20is%3Aclosed%20
Not every new package submitted will get approved. After three months without activity in the corresponding PR, it gets "Stale" automatically. The maintainer can push a new version (or just rebase and force) to remove the "Stale" tag, indicating that they are still active/interested. But it's still not guaranteed for inclusion.