Re: [aur-requests] [PRQ#35359] Deletion Request for chowtapemodel.lv2-git Rejected
On 2022-06-20 21:18:41 (+), not...@aur.archlinux.org wrote: > Request #35359 has been Rejected by Muflone [1]: > > the chowtapemodel-lv2-git is newer and other packages depend on > chowtapemodel.lv2-git The only other package depending on chowtapemodel.lv2-git is a meta package, which can easily be adapted. Upstream [1] is a cross-plugin-type project and the maintainer of chowtapemodel.lv2-git has not been building (and refused to build) the other plugin types for ideological/political reasons. Building all plugin types in a split package is the only sane way to deal with this package, which chowtapemodel-git already provides (even though it is newer). This has been communicated in #archlinux-proaudio and I see no reason as to why to have chowtapemodel.lv2-git still be around. It has been clearly communicated with the author of chowtapemodel-git to add further maintainers (e.g. that of chowtapemodel.lv2-git) if they show interest. Going through the hassle of merging the packages is more work than is warranted given this situation IMHO. Best, David [1] https://github.com/jatinchowdhury18/AnalogTapeModel -- https://sleepmap.de signature.asc Description: PGP signature
Re: [aur-requests] [PRQ#35557] Merge Request for chowtapemodel-git
On 2022-06-20 21:18:06 (+), notify--- via aur-requests wrote: > Muflone [1] filed a request to merge chowtapemodel-git [2] into > chowtapemodel.lv2-git [3]: > > duplicated and newer package I do not think this is the best course of action here. See https://lists.archlinux.org/pipermail/aur-requests/2022-June/073287.html The overhead of merging these packages is not justified given that chowtapemodel-git already does the right thing. Best, David -- https://sleepmap.de signature.asc Description: PGP signature
Re: [aur-requests] [PRQ#36579] Deletion Request for audacity-release-git
On 2022-07-26 11:45:59 (+0200), Evert Vorster wrote: > -git packages are built on the user's system, whereas community > packages are binary only. > There is some use for a package that tracks the latest release branch > of git, as the user can change some settings before compiling and > installing. This is not an option with community packages. Packages in our official repositories can be built from source by anyone (see ABS [1] and asp [2]). > Also, this package will track the _latest_ release, so when there is a > new branch, this package will be updated to track that branch, and > that will surely get updates. The package in [community] also tracks the latest release (that can be built), which is why audacity-release-git duplicates this effort. It is highly questionable whether tracking release branches makes any sense, as upstream will turn them into releases fairly soon which means they will maybe track commits in between e.g. 3.x.1 to 3.x.2 only very shortly. Therefore when looking at the AUR rules of submission [3], the package either breaks the first rule if it packages the same version as audacity in [community] or breaks the third rule, when packaging a handful of commits (if any) in the short time between releases. Best, David [1] https://wiki.archlinux.org/title/Arch_Build_System [2] https://man.archlinux.org/man/asp.1 [3] https://wiki.archlinux.org/title/AUR_submission_guidelines#Rules_of_submission -- https://sleepmap.de signature.asc Description: PGP signature
