userguide/install: add info on arch-based install

[JSkier21]

userguide/install: add info on arch-based install

Make sure these boxes are signed before submitting your Pull Request -- thank you.

• I have read the contributing guide lines at https://suricata.readthedocs.io/en/latest/devguide/codebase/contributing/contribution-process.html
• I have signed the Open Information Security Foundation contribution agreement at https://suricata.io/about/contribution-agreement/
• I have updated the user guide (in doc/userguide/) to reflect the changes made (if applicable)

Describe changes:

• Add ArchLinux based install information to documentation.

[codecov]

Codecov Report

Merging #8789 (e70d8dc) into master (22485b3) will decrease coverage by 0.05%.
The diff coverage is n/a.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #8789      +/-   ##
==========================================
- Coverage   82.18%   82.14%   -0.05%     
==========================================
  Files         969      969              
  Lines      272739   272739              
==========================================
- Hits       224164   224033     -131     
- Misses      48575    48706     +131     

Flag	Coverage Δ
fuzzcorpus	64.16% <ø> (-0.13%)	⬇️
suricata-verify	60.32% <ø> (-0.04%)	⬇️
unittests	62.87% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

[jufajardini]

Hi there, thanks for this contribution :)

Could you please adjust the commit message so it will comply with our commit guidelines?
In short, something like userguide/install: add info on arch-based install works. The commit body is fine.

For our documentation, we're also trying to keep lines at a 79/80 characters limit, following Sphinx/Rst suggestions.

[catenacyber]

@JSkier21 are you planning on addressing the requested changes ?

[JSkier21]

Should be ready to go?

[jufajardini]

Should be ready to go?

We have to adjust character limit per line, and the commit message, but this is something that I can do, this time, if need be :)

[jufajardini]

Should be ready to go?

We have to adjust character limit per line, and the commit message, but this is something that I can do, this time, if need be :)

Hey @JSkier21 do you want me to fix this one up?

[JSkier21]

Should be ready to go?

We have to adjust character limit per line, and the commit message, but this is something that I can do, this time, if need be :)

Hey @JSkier21 do you want me to fix this one up?

Certainly please, if you don't mind. I haven't had time to delve into this much lately, but I'll try to take notes on what you do for next time 🙂

[jufajardini]

Should be ready to go?

We have to adjust character limit per line, and the commit message, but this is something that I can do, this time, if need be :)

Hey @JSkier21 do you want me to fix this one up?

Certainly please, if you don't mind. I haven't had time to delve into this much lately, but I'll try to take notes on what you do for next time slightly_smiling_face

Ok, I'll submit a new PR with the preferred way, then you can compare and get a better idea of the guidelines ^^

[jufajardini]

Changes requested incorporated in: #8972

[JSkier21]

Should be ready to go?

We have to adjust character limit per line, and the commit message, but this is something that I can do, this time, if need be :)

Hey @JSkier21 do you want me to fix this one up?

Certainly please, if you don't mind. I haven't had time to delve into this much lately, but I'll try to take notes on what you do for next time slightly_smiling_face

Ok, I'll submit a new PR with the preferred way, then you can compare and get a better idea of the guidelines ^^

Much appreciated, thank you!