Extracting importers requires extracting many things, let me know if I can go ahead

[hsanjuan]

If I got it right, extracting the importer module for re-use in ipfs-cluster to use it is going to require to additionally extract (because of intermodule deps):

• blocks
• blockservice
• exchange
• pin
• unixfs
• routing
• merkledag

This is a bit of work and I want to make sure we you are OK with it? Or would you rather do things (or have me do things) differently?

@whyrusleeping @Stebalien

[whyrusleeping]

@hsanjuan All of this sounds good except pin. I don't think that one is necessary quite yet, is it?

In any case, i'm 👍 for having these extracted.

[whyrusleeping]

how about: start working on this, do exchange+bitswap last. We're working on a fix to bitswap that will hopefully be the last piece before the 0.4.14 release. Once that release is in, we can merge all these extractions.

[hsanjuan]

There is a dep from blocks/blockstore to pin (removing a block needs a pinner to unpin, if I remember well).

I can't do exchange last because it's not the top dependency, but I can wait and do others in the meantime.

[hsanjuan]

@whyrusleeping what if I extract just the Pinner interface ?

[magik6k]

Extracting exchange+bitswap now will make #4333 a bit annoying to fix (not that it doesn't have enough conflicts now), AFAIK we wanted to merge 4333 after 0.4.14 is released. so that shouldn't block this for long

[hsanjuan]

@magik6k ack. not touching exchange for the moment.

[kevina]

I am also have outstanding fixed to few of those packages so I would appreciate it if we hold off a bit. #4693 (importer) & #4680 (unixfs)

[kevina]

Also what the motivation for separating these out?

[ZenGround0]

@kevina ipfs/notes#278

[magik6k]

This has happened (the package lives in https://github.com/ipfs/go-unixfs)