@navi
A deb/rpm repository isn't much more than that. You dump packages in a directory and run a single command to extract the metadata into an index file. 'createrepo' or its C reimplementation for rpm, 'dpkg-scanpackages' for deb. That's all that's *required*. You then export said directory over http or mount it and you can install these packages with all the dependency tracking.
@dalias @draeath @ska @SRAZKVT
A deb/rpm repository isn't much more than that. You dump packages in a directory and run a single command to extract the metadata into an index file. 'createrepo' or its C reimplementation for rpm, 'dpkg-scanpackages' for deb. That's all that's *required*. You then export said directory over http or mount it and you can install these packages with all the dependency tracking.
@dalias @draeath @ska @SRAZKVT
@navi
I mean yes if you're going to be serious about building a binary repository then higher-level tools like reprepro to track packages and their versions in different suites so that you get auto cleanup of old versions and easy metadata signatures are definitely useful, but they're absolutely not required.
@SRAZKVT @dalias @draeath @ska
I mean yes if you're going to be serious about building a binary repository then higher-level tools like reprepro to track packages and their versions in different suites so that you get auto cleanup of old versions and easy metadata signatures are definitely useful, but they're absolutely not required.
@SRAZKVT @dalias @draeath @ska
- replies
- 1
- announces
- 0
- likes
- 1