| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
Freenode appears to be imploding.
Signed-off-by: Philip Withnall <pwithnall@endlessos.org>
|
| |
|
|
|
|
| |
Came up on #fedora-iot channel.
|
|
|
|
| |
Since the topic of Debian+ostree-for-host comes up fairly often.
|
| |
|
| |
|
| |
|
|
|
|
| |
We should link to the target and not the symlink.
|
|
|
|
|
|
| |
BuildStream no longer uses libostree internally (see
https://gitlab.com/BuildStream/buildstream/issues/387). It still
has first class support for interoperating with libostree repos.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Update this to mention the 3 Fedora derivatives, RHEL CoreOS etc.
Create 3 sections:
- OS/Distributions
- build tools
- rpm-ostree/flatpak
Closes: #1895
Approved by: dustymabe
|
|
|
|
|
| |
Closes: #1860
Approved by: jlebon
|
|
|
|
|
| |
Closes: #1802
Approved by: rfairley
|
|
|
|
|
|
|
|
| |
Since rust-libostree now exists too, let's make sure people
know about it.
Closes: #1762
Approved by: jlebon
|
|
|
|
|
|
|
|
|
|
|
| |
Let's get practical faster in the manual and have a simple "Hello World"
example right off the bat to hopefully make it easier to grok how OSTree
works.
Also some minor tweaks on wording around comparisons to git.
Closes: #1581
Approved by: cgwalters
|
|
|
|
|
|
|
|
|
|
| |
Basically it wasn't clear that the man pages and API doc
remain LGPLv2.
Closes: https://github.com/ostreedev/ostree/issues/1456
Closes: #1574
Approved by: smcv
|
|
|
|
|
|
|
|
|
|
| |
Because `README.md` also gets rendered into the docs, we need
to link directly to github.
Closes: https://github.com/ostreedev/ostree/issues/1534
Closes: #1554
Approved by: jlebon
|
|
|
|
|
|
|
|
|
|
| |
This will allow the text to be used in Wikipedia for example; it
also just makes more sense for documentation than the LGPLv2+.
Closes: #1431
Closes: #1432
Approved by: jlebon
|
|
|
|
|
|
|
|
| |
This is an example of a tool using libostree to cache and share
build results.
Closes: #1360
Approved by: cgwalters
|
|
|
|
|
|
|
|
| |
I find "libOSTree" awkward to type and really to look at. Let's be nicer on
people's pinky fingers and eyes and drop it all down to lowercase.
Closes: #1093
Approved by: jlebon
|
|
|
|
|
|
|
| |
The old wiki only contains link back to readthedocs.
The link to is useless.
Closes: #1050
Approved by: cgwalters
|
|
|
|
|
|
|
|
|
| |
Add meta-updater and QtOTA, and delete OpenEmbedded since it's implied by the
first two. Merge rpm-ostree + Atomic Host since they're close. Clarify
gnome-continuous a bit.
Closes: #700
Approved by: jlebon
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There are many motivating factors. The biggest is simply that at a practical
level, the command line is not sufficient to build a real system. The docs say
that it's a demo for the library. Let's make that more obvious, so people don't
try to use `ostree admin upgrade` for their real systems, and also don't use
e.g. `ostree commit` on the command line outside of test suites/quick hacking.
This change will also help clarify the role of rpm-ostree, which we will likely
be renamed to "nts". Then use of the term "ostree" will become much clearer. And
similarly for other people writing upgraders, they can say they use libostree.
I didn't try to change all of the docs and code at once, because it's going to
lead to conflicts.
The next big steps are:
- Rename the github repo (github will inject a redirect)
- Look at supporting a build where we don't do `ostree admin`, or at least
it's only built for tests. We may want to split it off as a separate binary
or so? That way people with their own upgraders don't need to ship it.
Closes: #659
Approved by: jlebon
|
|
|
|
|
| |
Closes: #397
Approved by: cgwalters
|
|
|
|
|
|
|
| |
I'm mostly just testing some Homu updates.
Closes: #299
Approved by: cgwalters
|
|
|
|
|
|
|
|
|
|
|
| |
I was going through the new version of the docs and noticed a few
problems. Mostly URLs that aren't linked, extra whitespace, and a few
mis-spellings.
I ran the files through `aspell check` and made some manual changes
myself.
These changes were tested locally with `mkdocs serve`
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I don't much like Docbook (and am considering converting the man pages
too), but let's start with the manual.
I looked at various documentation generators (there are a lot), and
I had a few requirements:
- Markdown
- Packaged in Fedora
- Suitable for upload to a static webserver
`mkdocs` seems to fit the bill.
|
|
|
|
|
|
|
| |
I'd like to migrate content from the GNOME wiki, as frankly the wiki
is crap. Markdown in git is better in every way.
Start by fleshing out the README.md to be more useful.
|
|
|
|
| |
Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Put in links to the wiki and the git repository for OSTree
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
It just sounds better.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
Skip the "how do we build" for now.
|