Fulltext results:
- coding_style_guidelines
- delines should be followed for all new code. In general, code can be considered “new code” when it makes up about 50% or more of the file(s) involved. This is enough to break precedents in the existing code and use the current style guidelines. <code c> /* * St
- wiki_standards_syntax
- ====== Documentation Formatting Syntax ====== [[doku>DokuWiki]] supports some simple markup language,... s page contains all possible syntax you may use when editing the pages. Simply have a look at the sour... e two backslashes followed by a whitespace or the end of line. This is some text with some linebreaks... at the two backslashes are only recognized at the end of a line\\ or followed by\\ a whitespace \\this
- packaging_guidelines
- **Hyperbola Packaging Guidelines** is the commitment that we, the Hyperbola Project, make to the Free Software Community in general and our users in particular. It is because of... bution Guidelines]]. They do not include or recommend non-free software or documentation and do not provide any type of support for the installation or ex
- hyperbola_roadmap
- ~~REDIRECT>en:manual:contrib:hyperbolabsd_roadmap~~
- git_contribution_guide
- === ===== SSH ===== == for the remote git management you have these two commands: == <code bash> ssh... olor #0B71B9/#DDF1FF>'make'</color> for example when it says <color #B90B0B/#FFDDDD>'Please specify t... er name for example <color #0B71B9/#DDF1FF>'documentation'</color> is the folder for many repositories like guide.git were i have uploaded my file then it prints Please specify the name of the Git repo
- packager_setup_guide
- Y="user-id"|' -i /etc/makepkg.conf </code> ==== Generate new checksums ==== <code bash> $ updpkgsums... $ doas librechroot clean-repo </code> ==== Build environments: ==== <code bash> $ doas librechroot -A x86_64 -n x86_64 make </code> <code bash> $ doas ... ults/makepkg.conf.i686 -n i686 make </code> ==== Enter Container ==== <code bash> $ doas librechroot