* rework relationship between runtime and cfg
* separate runtime from cfg
* simplify instantiation logic
* move installer to appropriate package
* move operator to sync package
* add tests for srcinfo service
* consolidate srcinfo service in sync
* add logger to srcinfo
* add logger to preparer
* remove unused text functions
* remove remaining text.* from srcinfo
* remove global logger parts
* remove global org method exports
* remove global logger
* move text->input
* add rule to prevent fmt.Print
* update golangci go version
* remove outdated FAQs
* remove outdated FAQs
* Updated Readme to include note about dependencies
Per issue #1142 I've added a note to the readme to let users know they'll need to install `base-devel`.
* Update README.md
* Update README.md
Clarified note regarding base-devel.
* README grammar, spelling, rewording, organizing
- Add "Objectives" section to group objectives.
- Transform Objective/Feature section bullets into action phrases.
- Fix yay/yaourt/etc capitalization. Italicize and follow ArchWiki style.
- Clearly identify the two Install section options with similar wording.
- Reorganize and reword Contributing section.
- Fix wording in last Code Style section sentence.
- Fix misc FAQ wording.
- Use same style for all FAQ issue links.
- Change link in "skipping packages" FAQ item to ArchWiki partial upgrade.
- Fix FAQ aur-only/repo-only cmd example line-spacing.
- Remove yay -Pu example since it is a deprecated (and wrapped) option.
* Fixup remove trailing newline in README file
* Add warning about editing files in vendor/
* Fixup revert italicized project/program names
* Change obj to Yaourt-style interactive srch/inst
* Change obj to Minimal dependencies
* Remove the limit-to-pacman deps feature
* Revert init-install sentence, but add "alternatively"
* Add provide-handling bullet to features
* Revert aur/repo-only FAQ item to one line
* Format cmd line examples similar to man page format
* Revert interface-for-pacman objective
* Mention dep instead of just saying don't touch
* Merge gopath into the build stage
Setting the gopath is more of a note than a step. It is not required and
I would expect most people can simply ignore it.
* Reword dependencies section.
The contributing section should be information and say what dependencies
are needed. There's no need to tell the user how to install them, they
can figure that out themselves.
Also mention git as a dependency.
* Tweak headings and drop numbers
Similar to the last commit. The headings should be
informative "Code Style", not commanding "Check code".
* yay -> Yay
Be more consistent when writing Yay as a name.
* Use ### instead of #### in Contributing
These are real subheadings, #### looks too small.
* Add support section
