Hi everyone, Kudos to Tim for all the updates these past few weeks! There has been a bit of a learning curve (e.g., creating pull requests in the new Gitea instance, verifying that all our subscriptions transferred correctly from pipermail to hyperkitty, or reinstalling the pmwiki plugin that generates a table of contents), but for the most part all the new services appear to be working smoothly. On Tue, 23 Jun 2020 Tim wrote:
- Advertising. I know, that sounds like selling out, but I mean more in a way of seeking attention from youtubers etc that spread the word.
One side effect of the bridge between IRC channels and Matrix rooms might be an increased visibility of CRUX in the wider world. But we've already run into some reports of abandoned Matrix rooms still advertising CRUX 3.6, so it might need more work to fully unify these two chat protocols. Despite prologic's misgivings about hurting CRUX's design if we change too many things, and Erich's warning that "the benefit might be smaller than expected", I can't see any harm in opening up the CRUX chat to Matrix users.
- some saner defaults for pkgadd/pkgmk/prt-get.. - runscripts by default? - writelog with rmlog_on_success by default? - advertise /var/lib/prt-get.aliases more prominently
I do find it odd that prt-get.aliases is so poorly documented. None of the man-pages installed by prt-get even mention this file, and the example that we distribute under /etc does not demonstrate the one-line mechanism for declaring that a package can serve as a replacement for more than one dependency: https://git.crux.nu/tools/prt-get/src/branch/master/src/pkgdb.cpp#L83 Only by inspecting the source code will the user discover the possibility of writing a line with a comma-separated list of dependencies satisfied by a given package. If the lack of documentation means that nobody has been writing alias lines like that, then we've been allocating memory to the private variable m_splitAliases for no good reason; it would be simpler just to ask the user to put the information on separate lines of prt-get.aliases. In the fork of prt-get that I've been working on, some of the new capabilities include: - do something useful with the optional dependencies line - support Alan's --group flag to abort an operation if one target fails - remove build log when uninstalling a port - handle correctly a mix of installed and not-yet-installed targets passed as arguments to 'install' or 'update' (FS#1910) - respect --install-root when runscripts is enabled If any of these features sound interesting, feel free to download my forked repo and try it out. Perhaps later this weekend I'll get around to adding the feature that lets the 'listorphans' command take aliases into account, so that pkgfoster does not prompt for removal of a package that actually satisfies a dependency. On Wed, 24 Jun 2020 Steve Volumetric wrote:
adding other ports-collections, take romster for instance, AFAIK the process to add a collection is a manual process and I can't just one-line it.
Yesterday's IRC discussion mentioned sepen's portdbc tool, which allows you to do a one-liner like portdbc getup baguette | doas tee /etc/ports/baguette.httpup (assuming you know the name of the collection you want to add). Searching for ports by name does not work with the latest rewrite of the portdb, but jaeger gave us a shell function to fill that gap: https://libera.irclog.whitequark.org/crux/2024-03-15#36004199; On Thu, 25 Jun 2020 Steffen Nurpmeso wrote:
I like the handbook. The wikis of the world are terribly outdated or incomplete, this one is, too. You find some pearls, but mostly...
I agree with Steffen. It's easy to criticize a wiki for omitting a page that would have addressed your current question directly. But a handbook that can be read from start to finish in a few hours is better at getting the new user oriented to the CRUX way of doing things. With the solid base of understanding imparted by the handbook, a new user is empowered to search more intelligently for answers in the upstream documentation. If they eventually decide to share what they learned by creating a page on the CRUX wiki, great, but there's no expectation that new users should contribute in that manner. Contributions in the form of bug reports and suggestions to the port maintainers are arguably more valuable (hence the switch to Gitea for its increased user-friendliness). On Mon, 4 Mar 2024 Joseph Bennie wrote:
A synopsis of the recent changes would be of interest. maybe another outlining tasks for 24/25 ?
Some time ago I started a TODO page for the next release (https://crux.nu/Wiki/TODO37-1). It's impressive to see how many of those bullet points have already been addressed! In short, Tim's comment "thanks to the core team for their hard work!" deserves to be repeated. They carry out their work in dignified silence, refraining from drawing attention to themselves but letting a rock-solid distro and a no-nonsense website testify to their labors. Cheers, John