joborun/web
2
1
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

xz to lz

Browse source
This commit is contained in:
joborun linux 2023-03-27 17:24:04 +00:00
parent c80f9e11a1
commit 2e856df629
1 changed files with 4 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

8
repos.md
View file

@ -21,15 +21,15 @@ This is optional but we test each package before we send it up to the repository
#### Example: ####
<pre>2.5M Dec 21 18:53 /var/cache/jobcore/coreutils-9.0-02-x86_64.pkg.tar.xz
2.5M Jan 10 15:17 /var/cache/jobcore-archive/coreutils-9.0-01-x86_64.pkg.tar.xz</pre>
<pre>2.5M Dec 21 18:53 /var/cache/jobcore/coreutils-9.0-02-x86_64.pkg.tar.lz
2.5M Jan 10 15:17 /var/cache/jobcore-archive/coreutils-9.0-01-x86_64.pkg.tar.lz</pre>
We changed our release numbering convention around Dec20th2021 to just adding a 0 in front of the Arch release. So if you see arch coreutils-9.0-3 and we have coreutils-9.0-02 we need to run an upgrade and see why Arch upgraded as well.
So say you built your first 20 jobcore packages and you want to make a local repository database:
<pre>
% sudo repo-add /var/cache/jobcore/jobcore.db.tar.gz /var/cache/jobcore/*pkg.tar.xz </pre>
% sudo repo-add /var/cache/jobcore/jobcore.db.tar.gz /var/cache/jobcore/*pkg.tar.lz </pre>
You can substitute in your pacman.conf our osdn mirror with your local repository and you will see you have 20 pkgs in there, the ones you made.
@ -37,7 +37,7 @@ What happens when pacman tries to install one of those? If first "downloads" th
To avoid this, do as we do:
<pre>sudo ln -s /var/cache/jobcore/*.pkg.tar.xz /var/cache/pacman/pkg/</pre>
<pre>sudo ln -s /var/cache/jobcore/*.pkg.tar.lz /var/cache/pacman/pkg/</pre>
So when pacman tries to install the package it sees already a copy in your local directory (even though it is just a link) and doesn't try to download copy from your repository.