Hi All,

I wanted to throw in too that I agree that there should perhaps be separate handling for "personal" ports of things.  I've spun through a few of them and, as expected, get mixed results.  I suppose the argument could be made "We already have core, opt, contrib , etc; anything else should be treated like the wild-west"  

I personally am mostly happy with how things are now..with the only exception being that (forgive me I forget the unit term) 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.

I would hope there'd be like a Col-get in addition to Prt-get where I could :

col-get install romster

and then prt-get the ports inside that collection.

Or maybe that already exists and i'm totally off track.

Other than that, Crux does all the things I want it to and , of absolutely paramount importance, it does not do the things I never want my OS to do.

Someone mentioned updating the website crux.nu,  I have mixed feelings.  In a world of flashy interfaces and visual chaos, crux.nu is kind of a nice oasis of simplicity.  I absolutely would not change how it functions in terms of presenting information, though I do agree manuals/wikis could be more supportive and explanitory.

On Wed, Jun 24, 2020 at 3:21 AM Tim <tbier@posteo.de> wrote:
Hi Erich, hi everybody

On Wed, 24 Jun 2020 09:49:59 +0200 (CEST)
Erich Eckner <crux@eckner.net> wrote:

> >     - cgit is fine but something like gitlab could combine that
> >     ...
> This may sound nice, but it will also be a lot of work - and the
> benefit might be smaller than expected.

Well, I am not saying all the features are needed, but migrating the
git repos is swiftly done, tickets from flyspray might be a bit harder
but it's not like we are having a lot of tickets open and flypsray
could still be accessible as read-only for history reasons if there is
no way of importing the entire db.
CI is just a wish :) I know christmas won't come early.

The basic idea is to have a platform that makes our development process
more visible and maybe a bit more agile? (don't stone me, I'm not
whipping you through a sprint :))

> I think, it would help to be able to sort by version in the portdb
> search. My usual approach is: "I need port 'x'" -> search for 'x' in
> the portdb
> - -> look at the 3 results for 'x' -> take the newest -> try to build
> -> add it to my repo -> try to improve further (e.g. newer version)

I do it the same way, and I imagine that most CRUXers do it like that.
A function like this surely would help to guide newbies to pick the
best decision.

> If everyone is encouraged to create their own repo (and if it's
> really easy), then we will have one repo per user in the end - and I
> don't see, why that would be bad. I think, it's hard to mark repos as
> a whole as "good content" or "bad content" - I, for example, have
> definitely "bad content" in my repository: Stuff, that noone besides
> me uses. But otoh, I think, this does not apply to *everything* in my
> repo :-)

I really try to keep my public ports, as clean as possible. Same counts
for my non public ports, but the rules are less strict there :-)
While encouraging users to get active, I feel like it's also important
to encourage a good quality. Those "work on my system" kind of ports
really aren't fun to deal with and will drive newbies away, if they
aren't able to get out of that mess or get stuff running like it is
supposed to.

Have a great day,

Tim
_______________________________________________
CRUX mailing list
CRUX@lists.crux.nu
https://lists.crux.nu/mailman/listinfo/crux