> From a bit of testing, starship is quite neat - not necessarily for ksh > purists, > but I'm quite enjoying it in combination with fish and work with git repos (no > support for jj yet, at least not out of the box). Indeed, maybe someone could look into ksh support on top of it ;) but yeah I also use fish for a while and starship makes my configuration much shorter overall lol Regarding Jujutsu: https://github.com/starship/starship/pull/7224
>> but also if I may, what purpose does WANTLIB serve >> here? > >man 7 library-specs > >It serves the same purpose here as it does everywhere :-) Thanks, forgot about that one but indeed it makes sense that it appeared to work as it only seems to require system libraries after all >It gets easier once you committed the steps of updating a rust port to muscle >memory ;-) I'm sure, but I'm more a little bit baffled coming from go-module(5) at the whole rigmarole of adding the licence comments to crates.inc after the fact (which seems to require parsing the existing crates.inc, redirecting the output elsewhere, and then overwriting the file...?) so I'd love a bit more insight into why it is so different since as much as I dug at the docs, I couldn't find much of an explanation. In any case, this was more just leaving some information here for a potential independent discussion later on re. cargo-module(5) and its documentation, I know it isn't fully related to this port in particular. >Porting is arguably a bit more involved than just making stuff compile: After >all the whole point is to make it build and install for everyone, not just for >yourself. Agreed, I just meant the build step in making the package for everyone :) >Just remember: >https://www.openbsd.org/images/hackathons/p2k9.gif Good one, I'm saving it~
