Date: Mon, 30 Oct 2023 15:30:17 +0000 From: Doug Rabson <dfr@rabson.org> To: Baptiste Daroussin <bapt@freebsd.org> Cc: pkgbase@freebsd.org Subject: Re: official packages Message-ID: <CACA0VUjH2kcp-ZnhHUtZGDgA2v3zqEeqBNJc_XOvJKmiACvjdA@mail.gmail.com> In-Reply-To: <lkxbabsbm2odlus2re6qpns4a5wa3mgk2zoljzxhc3jbgifs6g@gpepvsamf36i> References: <lkxbabsbm2odlus2re6qpns4a5wa3mgk2zoljzxhc3jbgifs6g@gpepvsamf36i>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --]
On Mon, 30 Oct 2023 at 14:25, Baptiste Daroussin <bapt@freebsd.org> wrote:
> Hello everyone,
>
> The project has started building and populated official packages for
> pkgbase.
>
> For people interested: just create a new repo like this:
>
> FreeBSD-base {
> url: pkg+https://pkg.freebsd.org/${ABI}/base_latest
> signature_type: "fingerprints"
> fingerprints: "/usr/share/keys/pkg"
> mirror_type: "srv"
> }
>
> the current build was built last friday, everything is ready to be able to
> publish in regular basis.
>
> Here is my proposal for main and stable branches:
> - build everything in a end less loop (to detect failures as soon as
> possible) and
> twice a day at a fix time, publish it under "base_latest"
> - every sunday take the last built snapshot and publish it under the
> base_weekly
> snapshot at a predictable time.
>
> For releng:
> - built it in a end less loop and publish straight each time there was
> changes
>
> For end users on stable/main the default would be: to end on the
> base_weekly
> (does not exists yet) repo, but users can if needed switch to base_latest.
>
> For base_release_X for release users base_release_0 for 14.0 for example.
>
> all the failures will be published in this mailing list!
>
> Is it ok with you?
>
This is great news, thanks for all the work getting this far. I see
packages available for 15 already. If I understand you correctly, packages
for stable/13 and stable/14 are planned - is that right?
[-- Attachment #2 --]
<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, 30 Oct 2023 at 14:25, Baptiste Daroussin <<a href="mailto:bapt@freebsd.org">bapt@freebsd.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">Hello everyone,<br>
<br>
The project has started building and populated official packages for pkgbase.<br>
<br>
For people interested: just create a new repo like this:<br>
<br>
FreeBSD-base {<br>
url: pkg+<a href="https://pkg.freebsd.org/$%7BABI%7D/base_latest" rel="noreferrer" target="_blank">https://pkg.freebsd.org/${ABI}/base_latest</a><br>;
signature_type: "fingerprints"<br>
fingerprints: "/usr/share/keys/pkg"<br>
mirror_type: "srv"<br>
}<br>
<br>
the current build was built last friday, everything is ready to be able to<br>
publish in regular basis.<br>
<br>
Here is my proposal for main and stable branches:<br>
- build everything in a end less loop (to detect failures as soon as possible) and<br>
twice a day at a fix time, publish it under "base_latest"<br>
- every sunday take the last built snapshot and publish it under the base_weekly<br>
snapshot at a predictable time.<br>
<br>
For releng:<br>
- built it in a end less loop and publish straight each time there was changes<br>
<br>
For end users on stable/main the default would be: to end on the base_weekly<br>
(does not exists yet) repo, but users can if needed switch to base_latest.<br>
<br>
For base_release_X for release users base_release_0 for 14.0 for example.<br>
<br>
all the failures will be published in this mailing list!<br>
<br>
Is it ok with you?<br></blockquote><div><br></div><div>This is great news, thanks for all the work getting this far. I see packages available for 15 already. If I understand you correctly, packages for stable/13 and stable/14 are planned - is that right?</div><div> </div></div></div>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACA0VUjH2kcp-ZnhHUtZGDgA2v3zqEeqBNJc_XOvJKmiACvjdA>