User Details
- User Since
- Apr 18 2014, 5:23 AM (604 w, 17 h)
Yesterday
Wed, Nov 12
sorry this tool is confusing, and swallowing your properly formatted patch, maybe it is just me would do not know how to properly retrieve this patch properly, in the mean time if you can send it to me by email, I will be able to push it straight thanks.
good catch thank you, can you provide me a git format-patch generated file so you can get proper credit ?
Tue, Nov 11
Considering that if one sets UseBlocklist yes and blocklistd is not installed at all, will just result with the same behaviour as with blocklistd installed but not started I think the is ok to split the packages this way.
Mon, Nov 10
Sun, Nov 9
Fri, Nov 7
the ports tree is a framework to build packages, if we are to build sbom on a distribution of packages we don't want to work on the framework which builds repositories, but on the package repository side. Meaning in the ports tree we need to make sure we collect enough metadata so that packages themselves have enough metadata for a tool like this one to collect the informations from the packages directly and not from the sources.
Wed, Nov 5
to be honnest I am not a big fan of this being adding to the ports tree, because usually the sbom analysis (my use case at least is on what would be reployed, so it needs to happen and the packaging level more than at the source level imho.
Tue, Nov 4
Fri, Oct 31
Wed, Oct 29
Tue, Oct 28
Sat, Oct 25
Fri, Oct 24
Thu, Oct 23
Tue, Oct 21
LGTM and I like @kevans proposal.
Mon, Oct 20
Fri, Oct 17
should fix the issues spotted by scaleway people as well
Oct 10 2025
Oct 7 2025
this is not for all case because people may have multiple checkouts of the source tree (other than /usr/src) this is good only for releases.
Oct 3 2025
Sep 30 2025
Sep 29 2025
Sep 25 2025
Sep 24 2025
The main goal of mdo(1) I had in mind when I implemented is cases where on some system operators have to run commands as another user, like I connect ssh me@machine, then I need to do some things as nextcloud user. so basically every people in the "admin" group can run a command as nextcloud.
being able to have on this machine nextcloud the default user mdo switches to make it more user friendly, but yes this is sugar, not a strong requirement.
I am puzzled here, yes I like this, as it makes mdo(1) way more versatile, but I am also wondering if we are not here a little bit over thinking this, I get the completeness of it, but I fail at seeing a practical use case for this, and this adds lots of complexity to the code. Caan you share example on how you expect this to be used?