What if we removed the concept of package lists for tags in Koji?
In other words, we would remove these concepts:
koji add-pkg ...
koji remove-pkg ...
It's a lot of manual work to keep package lists (especially owners!)
up-to-date. It's a simpler workflow if users can just:
Step 1) Create a dist-git repo for a package
Step 2) Perform a build of the package
This would eliminate the following steps:
- "Discover who the human owner will be"
- "Ensure that human owner has a user account in Koji's database
(possibly asking them to pre-create their account)"
- "Keep the ownership records up-to-date over time" (for example:
so-and-so has left the Perl team, how should that developer update
Koji to stop getting emails?)
- Ken
Show replies by date