On Wed, Feb 04, 2026 at 02:46:32PM +0000, Stuart Henderson wrote: > On 2026/02/04 11:03, Raphael Graf wrote: > > > > > > there are a *lot* of binaries, with fairly generic names, some of which > > > > conflict with existing ports: > > > > > > > > go-cs-1.1:sysutils/go-cs:/usr/local/bin/cs > > > > gpstk-2.10:geo/gpstk:/usr/local/bin/scale > > > > > > > > I see Debian splits into a main package (with cs, csbeats, csdebugger, > > > > csound) and csound-utils with the rest, which might be a reasonable > > > > approach (then just the -utils subpackage could conflict). Otherwise > > > > they'd probably need to be installed in a different dir. > > > > > > I think using a subpackage for the utils is reasonable. There is now a > > > main package and a utils package. The utils package still does conflict. > > > Is this acceptable? > > > > > > > Sorry, I have changed my mind regarding the utility programs that > > cause conflicts. I think it is better to not install them at all as > > most of them can be invoked through the csound executable: > > $ csound [-U utilname] [flags] [filenames] > > > > Regarding the remaining utils, upstream says: > > "Most of them will be out of the code base before the release. > > Possibly csb64enc and makecsd will be kept ..." > > (https://github.com/csound/csound/issues/2452) > > > > In the attached version, I've commented everything out in PLIST > > (except csb64enc and makecsd), and added a note in README. > > There is no subpackage anymore, and no conflict. > > > > > > this is generally looking pretty good to me. up to you about waiting > for the release vs adding as a beta - I wouldn't object to adding as a > beta.
Adding it as a beta has the advantage that it may get more testing. kili@, are you also ok with it being imported now? > > two small comments, > > DIST_TUPLE = github csound csound 7.0.0-beta.12 . > > portroach is not very good at picking up new versions with DIST_TUPLE, > if you wanted that to work then stick to the old GH_* This is good to know. > > -DBUILD_STATIC_LIBRARY=ON \ > > is the static lib actually useful or just dead weight in the package? Somehow, BUILD_STATIC_LIBRARY=ON is needed for the tests.
