Replies: 2 comments 2 replies
-
There are no licensing issues, as your software appears to be GPL while BSDCoreUtils is BSD, you're allowed to mix software from said licenses without any issues. I'm fine with it and thank you for using it :). |
Beta Was this translation helpful? Give feedback.
1 reply
-
@DiegoMagdaleno I got a few minor warnings when compiling with the default flags in my meson build. Would you like me to try and fix them on your repo?
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Note to self:
gcc -Wall -I../../compat/include rm.c ../../compat/src/pwcache.c ../../compat/unkown_brother/strlcpy.c ../../compat/src/strmode.c -o rm
Over the last several years, I tried a few times to compile
rm
from GNUCoreutils (I never succeeded). I was able to do it in just a couple minutes using @DiegoMagdaleno / BSDCoreUtils.I'm thinking about using it for the purge feature of rmw. I was using my own code, then recently replaced it with a call to system(rm...), but now I realize that calling the binary for each file purged would be far too insane.
I think I'll wanna check with the maintainers before doing so though, just to make sure there are no licensing issues. I might just add BSDCoreutils as a submodule to keep everything intact, including all the licensing and docs included in that repo.
I'm also considering busybox but I haven't played it with that for a while and not sure yet what the process is for compiling
rm
.Beta Was this translation helpful? Give feedback.
All reactions