Radare2: Use git subtree for dependencies

Created on 4 Oct 2018  Â·  14Comments  Â·  Source: radareorg/radare2

Hello,

I think it would be easier to handle the dependencies in radare2 (mostly shlr/ folder) if we were using git submodules.
I think copy pasting is a bad practice and that we should use better development practices.

[EDIT] Actually I believe using git subtree is much better for our needs.

buildsystem enhancement

Most helpful comment

A friend of mine just learned me too alternatives:

Those are worth checking out.

All 14 comments

how many times we had this discussion? are you sure there's no other issue to track this? anyone tried to ask github to support submodules in the release tarballs? i dont want to push my own tarballs. also managing submodules will be a pain for many users, even if its good practices will introduce many new issues for many users. So until github doesnt supports it i dont have any plan in switching to submodules

I don't want to push my own tarballs.

Fortunately in 2018 there are tools such as Travis which can do that for you. Not an issue from my PoV.

Travis fails pretty frequently, and delegating the responsability to create tarballs to a third party implies a security issue in the distribution stage. also extra work to maintain/setup.

why not just mail github and ask for this feature

On 4 Oct 2018, at 15:01, xarkes notifications@github.com wrote:

I don't want to push my own tarballs.

Fortunately in 2018 there are tools such as Travis which can do that for you. Not an issue from my PoV.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/radare/radare2/issues/11730#issuecomment-427009455, or mute the thread https://github.com/notifications/unsubscribe-auth/AA3-lg9JUjsmcEKlpbpNgFpNxTZdxAlxks5uhgaYgaJpZM4XICIO.

@Maijin asked and there is no answer for now.
I think he should ping them again.

sgtm

On 4 Oct 2018, at 16:13, xarkes notifications@github.com wrote:

@Maijin https://github.com/Maijin asked and there is no answer for now.
I think he should ping them again.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/radare/radare2/issues/11730#issuecomment-427034924, or mute the thread https://github.com/notifications/unsubscribe-auth/AA3-lpgoreYhe1XA3UsjcijD5wUFrcn4ks5uhhefgaJpZM4XICIO.

A friend of mine just learned me too alternatives:

Those are worth checking out.

wait, maybe sub-tree can fix the issue though because as @xarkes explain, it's a copy just like we have now.

I created a test-case for subtree here:

The release contains the subtree in Github:

image

Another reason for not using submodules is because we will miss all the static source code analysis reports from Coverity. That's how i found many vulns in capstone, grub, gnu binutils, zip, .... we can't register more projects there

@radare have you read the proposed solution with subtree?

nope, im just focusing on the release. and this is not going to be in this release

On 12 Oct 2018, at 13:28, Maijin notifications@github.com wrote:

@radare https://github.com/radare have you read the proposed solution with subtree?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/radare/radare2/issues/11730#issuecomment-429294659, or mute the thread https://github.com/notifications/unsubscribe-auth/AA3-lsw3PP6V_QFG-3pJ4xct3dlHy-pCks5ukHztgaJpZM4XICIO.

So when you have time, read my message below then comment because this "we will miss all the static source code analysis " is not a problem with git subtree.

Seems like we're moving towards submodules see #15497

Was this page helpful?
0 / 5 - 0 ratings

Related issues

RazviAlex picture RazviAlex  Â·  4Comments

radare picture radare  Â·  8Comments

Manouchehri picture Manouchehri  Â·  3Comments

S01den picture S01den  Â·  4Comments

MariasStory picture MariasStory  Â·  6Comments