Skip to content

Conversation

@jfingerh
Copy link

plus some minor typo corrections.

@jfingerh
Copy link
Author

Notes on the changes:

As far as I can see, there is no variable named SCRIPT_DIR in any of the bash scripts in the ipdk/build/networking directory and its subdirectories. Thus it has no effect at all assigning a value to SCRIPT_DIR while running the install script.

It seems to me unnecessarily confusing to give instructions to clone the ipdk repo anywhere you want, and call it <CLONE-PATH>, and then the very first example of how to run the install script only works if you did it in the /git directory. It seems much less confusing to omit that option, and simply always use the -d <CLONE-PATH> in all choices shown. One less thing to get wrong for the reader.

@ffoulkes
Copy link
Contributor

ffoulkes commented Dec 4, 2023

@n-sandeep @5abeel
Can I get your feedback / approval / disapproval for this PR?


```bash
root@linux:~# SCRIPT_DIR=<CLONE-PATH>/ipdk/build/networking/scripts <CLONE-PATH>/ipdk/build/networking/scripts/host_install.sh
root@linux:~# <CLONE-PATH>/ipdk/build/networking/scripts/host_install.sh -d <CLONE-PATH>
Copy link
Contributor

Choose a reason for hiding this comment

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

I think this is a typo for SCRIPTS_DIR, which is referenced in host_install.sh.

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

Successfully merging this pull request may close these issues.

2 participants