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

[technical debt] Decouple MFS from UnixFS #8541

Open
3 tasks done
schomatis opened this issue Nov 5, 2021 · 0 comments
Open
3 tasks done

[technical debt] Decouple MFS from UnixFS #8541

schomatis opened this issue Nov 5, 2021 · 0 comments
Labels
kind/bug A bug in existing code (including security flaws) need/triage Needs initial labeling and prioritization

Comments

@schomatis
Copy link
Contributor

Checklist

Installation method

built from source

Version

.

Config

.

Description

The general theme of this issue is:

  • UnixFS should impelement the File System part of the stack, i.e., mapping local filesystem files, directories, links, etc. to IPFS/IPLD DAGs.
  • MFS should only implement the mutable layer of this filesystem DAG (i.e., MFS only adds the M to the FS).

The concrete part of this issue, local to the go-ipfs implementation, is to remove the MFS from the ipfs add command, limiting it only to the ipfs files one. Achieving this will point us in the right direction regarding the general theme above.

More specifically and as a starting point, we should remove the MFS root form the the Adder structure. This is not the permanent MFS root used in the ipfs files command (stored in the repo) but just an ephemeral directory needed to support basic FS operations resulting from the unwanted coupling of UnixFS/MFS.

@schomatis schomatis added kind/bug A bug in existing code (including security flaws) need/triage Needs initial labeling and prioritization labels Nov 5, 2021
@BigLep BigLep added this to the Best Effort Track milestone Mar 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug A bug in existing code (including security flaws) need/triage Needs initial labeling and prioritization
Projects
No open projects
Status: No status
Development

No branches or pull requests

2 participants