On Aug 29, 2025, at 10:28 PM, Joshua Root <[email protected]> wrote: > On 30/8/2025 00:26, Ryan Carsten Schmidt wrote: >> For example a user who wants cliclick just installs the port. It picks the >> right version for the OS version. This is simple for the user. The >> alternative is that a user of an old OS would have to know to install a >> hypothetical cliclick4 instead. And the situation becomes complicated if the >> criteria change. For example, if I later figure out a way to offer version 5 >> to some older OS versions, how does the user who installed cliclick4 learn >> of that? > > I would suggest doing it a little differently: Offer a cliclick port which > installs no files but depends on cliclick4 or cliclick5 depending on the OS > version.
+1 to this. >> The separate versioned ports strategy also doesn't always work well because >> it takes continual effort to keep them in sync. The postgresql ports for >> example are all a little different from one another because at various times >> a fix or a reformat only got applied to one of them but not the others. > Subports can often make this a bit easier. There are also cases where we do this where we probably don't need to be going through the effort to do so (I'm looking at you, perl5). -- Daniel J. Luke
