Plan for separating libbpfgo from tracee repo #727
Replies: 4 comments 6 replies
-
@eyakubovich, @brancz As contributors, and presumably consumers of libbpfgo, does this sound good to you? |
Beta Was this translation helpful? Give feedback.
-
I'd just move the 2nd step to be last (removing). good point about removing from head shouldn't affect existing users who use the commit hash. |
Beta Was this translation helpful? Give feedback.
-
Alright #728 will be the last commit into libbpfgo before separating it into its own repo. I will cut a release as soon as I make that repo public. As for tracee, I will update usage to the new repo, then subsequently remove libbpfgo from it. |
Beta Was this translation helpful? Give feedback.
-
Get it while it's hot! https://github.com/aquasecurity/libbpfgo |
Beta Was this translation helpful? Give feedback.
-
I'd like to separate libbpfgo from this repo. Since it's already its own go module we would better be able to serve projects that want to import it by having it logically separated.
This entails
Points that I want to be very careful of:
Beta Was this translation helpful? Give feedback.
All reactions