nimbus/README.md

125 lines
3.1 KiB
Markdown
Raw Permalink Normal View History

2024-01-11 04:47:01 +00:00
<!-- SPDX-FileCopyrightText: 2022-2024 Anna <cyber@sysrq.in> -->
2022-06-25 21:53:50 +00:00
<!-- SPDX-License-Identifier: CC0-1.0 -->
nimbus
======
2023-05-02 14:24:02 +00:00
[![Build Status](https://drone.tildegit.org/api/badges/CyberTaIlor/nimbus/status.svg)](https://drone.tildegit.org/CyberTaIlor/nimbus)
[![OpenSSF Best Practices](https://www.bestpractices.dev/projects/8267/badge)](https://www.bestpractices.dev/projects/8267)
2023-05-02 14:24:02 +00:00
2022-06-25 21:53:50 +00:00
**nimbus** is a **Nim** **bu**ild **s**ystem. You can also call in NimBS. Nimja
2022-07-13 10:31:56 +00:00
would also be a clever name but it's already taken (turns out the name "nimbus"
is taken two times already but nobody cares yet).
2022-06-25 21:53:50 +00:00
2022-07-13 13:23:32 +00:00
* [Read the manpage online][man]
* Example use:
* [nimble.eclass][nimble.eclass]
* [dev-nim/\* ebuilds][dev-nim]
2022-07-13 12:05:51 +00:00
[man]: https://docs.sysrq.in/nimbus
2022-07-13 13:23:32 +00:00
[nimble.eclass]: https://gitweb.gentoo.org/repo/proj/guru.git/tree/eclass/nimble.eclass
[dev-nim]: https://gitweb.gentoo.org/repo/proj/guru.git/tree/dev-nim
2022-07-13 12:05:51 +00:00
2022-06-25 21:53:50 +00:00
Raison d'être
-------------
[nimble](https://github.com/nim-lang/nimble) is a great tool for development but
it does not get on well with system package managers.
This project is intended to be used with traditional package managers (primarly
with Gentoo's Portage). But maybe it'll be useful for other purposes too.
2024-01-11 04:47:01 +00:00
Development status
------------------
This software is considered [completed][ddv-post] and stable. No new features
are planned, however there will be releases for bug fixes and compatibility
updates.
[ddv-post]: https://drewdevault.com/2021/01/04/A-culture-of-stability-and-reliability.html
2022-06-25 21:53:50 +00:00
Dependencies
------------
2024-01-11 04:47:01 +00:00
This software has no build dependencies other than the Nim standard library.
2022-06-25 21:53:50 +00:00
**nimbus** only generates `build.ninja` files, so you'll need [ninja][ninja]
or [samurai][samurai] to use it.
[ninja]: https://ninja-build.org/
[samurai]: https://github.com/michaelforney/samurai
Installing
----------
* Using nimble:
`nimble install`
2023-11-25 08:39:31 +00:00
* Using just Nim compiler (expert):
2022-06-25 21:53:50 +00:00
2023-05-02 14:21:43 +00:00
```sh
nim c src/nimbus
nim c src/txt2deps
```
2022-06-28 23:01:47 +00:00
Testing
-------
```sh
$ testament all
```
2022-06-25 21:53:50 +00:00
2022-07-13 11:45:37 +00:00
Packaging
---------
You can track new releases using an [atom feed][atom] provided by GitHub.
[atom]: https://github.com/cybertailor/nimbus/releases.atom
2022-06-25 21:53:50 +00:00
Contributing
------------
2024-01-11 04:47:01 +00:00
Patches and pull requests are welcome. Please use either
[git-send-email(1)][git-send-email] or [git-request-pull(1)][git-request-pull],
addressed to <cyber@sysrq.in>.
2022-06-25 21:53:50 +00:00
Your commit message should conform to the following standard:
```
file/changed: Concice and complete statement of the purpose
This is the body of the commit message. The line above is the
summary. The summary should be no more than 72 chars long. The
body can be more freely formatted, but make it look nice. Make
sure to reference any bug reports and other contributors. Make
sure the correct authorship appears.
```
2024-01-11 04:47:01 +00:00
[git-send-email]: https://git-send-email.io/
[git-request-pull]: https://git-scm.com/docs/git-request-pull
2022-06-25 21:53:50 +00:00
2022-06-29 11:10:09 +00:00
IRC
---
You can join the `#nimbus` channel either on [OFTC][oftc] or
[via Matrix][matrix].
[oftc]: https://www.oftc.net/
2023-11-21 23:41:30 +00:00
[matrix]: https://matrix.to/#/#nimbus:sysrq.in
2022-06-29 11:10:09 +00:00
2022-06-25 21:53:50 +00:00
License
-------
* BSD-3-Clause
* Apache-2.0 (`ninja_syntax.nim`)