Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Similar project #1

Closed
NiKiZe opened this issue Jul 25, 2018 · 3 comments
Closed

Similar project #1

NiKiZe opened this issue Jul 25, 2018 · 3 comments

Comments

@NiKiZe
Copy link

NiKiZe commented Jul 25, 2018

Hi,
Just want to let you know that I'm working on something similar, at least probably the same end goal.
See ipfs/notes#296
I'm currently working on getting a full IPFS mirror of the distfiles up and running at https://github.com/NiKiZe/Gentoo-distfiles-IPFS

I will close this issue directly after creating it, since it's not a real issue, just wanted to let you know.

@NiKiZe NiKiZe closed this as completed Jul 25, 2018
@piedar
Copy link
Owner

piedar commented Jul 25, 2018

Cool! I think your import script is better because it syncs directly from a distfiles mirror instead of downloading each package's sources one by one. I got bored running mine on all the packages...

I started on another project to mount ipfs filesystems, which could be complementary once the chunking situation is solved. It would also be cool to define a way to download and verify files by hash directly in the ebuild, possibly removing the need for additional Manifest files.

@NiKiZe
Copy link
Author

NiKiZe commented Jul 25, 2018

Regarding IPFS hash in ebuild, I think that is a bad place, for the same reason that other checksum are stored in Manifest instead of ebuild (the hash should be created by external tools from the data without needing manual modifications) So I'm voting for adding them to the Manifest, in the ipfs notes I mentioned you will find a link to the Gentoo forums where I have tried to explain this to some other people.
One middle ground is to generate full file to ipfs hash mappings which could be distributed separately. (which is on my todo list)

If ipfs mounts can be faster, than that's great! does official IPFS devs know about this project?
The chunking should "always" be done with 256K as it's the default so maybe you should run internal buffer for this? (I probably don't know what I'm talking about here but that is what I have understood so far)
This support writes as well, but read-only support should be good enough, and that should not have the chunking issues?
Is there IPNS support as well?

@piedar
Copy link
Owner

piedar commented Jul 25, 2018

Regarding IPFS hash in ebuild, I think that is a bad place, for the same reason that other checksum are stored in Manifest instead of ebuild (the hash should be created by external tools from the data without needing manual modifications)

My hope for that was to take full advantage of content addressing. But reading that forum thread I see there is no way Gentoo devs will agree to start adding hashes to ebuilds in that fashion. But that's OK - I've found other things to work on and I'm not so worried about the distfiles problem at the moment.

The chunking should "always" be done with 256K as it's the default so maybe you should run internal buffer for this?

I tried that a couple ways in feature branches but it isn't stable yet. Hopefully upstream can solve it instead.

Is there IPNS support as well?

Not yet, but I think that will be the next big feature when I next get some time to work on it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants