Skip to content
This repository has been archived by the owner on Sep 1, 2022. It is now read-only.

Contrib: archiso profile for Kovri dev + testnet #808

Closed
wants to merge 1 commit into from

Conversation

coneiric
Copy link
Contributor

@coneiric coneiric commented Feb 8, 2018

Archiso profile and instructions for building a LiveUSB.
LiveUSB comes with everything a user needs to use, develop, and test Kovri.


By submitting this pull-request, I confirm the following:

  • I have read and understood the contributor guide in kovri-docs.
  • I have checked that another pull-request for this purpose does not exist.
  • I have considered and confirmed that this submission will be valuable to others.
  • I accept that this submission may not be used and that this pull-request may be closed by the will of the maintainer.
  • I give this submission freely under the BSD 3-clause license.

Archiso profile and instructions for building a Kovri LiveUSB.
LiveUSB comes with everything a user needs to use, develop, and test Kovri.
Copy link
Collaborator

@anonimal anonimal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not to snuff this contribution, but why should this be incorporated into the mainline branch? This PR is almost entirely unrelated to kovri. Can we keep the archiso stuff elsewhere and keep the kovri things here? Arch-maintained files should not be in the kovri tree.

I think an archiso is neat idea for when we have actual releases but having to rebuild for every system update until then?!...

# Build and install Kovri
cd /usr/src/kovri && KOVRI_DATA_PATH=/home/kovri/.kovri make -j$(nproc) release && make install
chown -R kovri:kovri /home/kovri
ln -sf /usr/src/kovri/build/{kovri,kovri-util} /usr/bin
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

make install installs into ~/bin/.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for catching that. Leftover from previous iterations.

@coneiric
Copy link
Contributor Author

coneiric commented Feb 9, 2018

Can we keep the archiso stuff elsewhere and keep the kovri things here?

I was thinking of starting a separate repo for this, and with your feedback this sounds like the right thing to do.

I think an archiso is neat idea for when we have actual releases but having to rebuild for every system update until then?!

100% agreed, failed to realize that this would cause rebuilds for changes unrelated to Kovri.

I'll move the archiso files into their own repo, and maintain them as a stand-alone project.

@coneiric coneiric closed this Feb 9, 2018
@anonimal
Copy link
Collaborator

I was thinking of starting a separate repo for this, and with your feedback this sounds like the right thing to do.

I think that would be awesome. We can add a link somewhere in the docs or contrib.

@coneiric coneiric deleted the archiso branch March 5, 2018 22:23
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants