From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: damien thiriet via ntg-context <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@xs4all.nl>
Subject: Re: OpenBSD binaries
Date: Fri, 4 Nov 2022 10:06:25 +0100 [thread overview]
Message-ID: <48939a61-ec6e-ed98-5aee-78bde80ff80f@xs4all.nl> (raw)
In-Reply-To: <01aa53fdda86caedf2ae7eab7f888a26@thiriet.web4me.fr>
On 11/4/2022 9:24 AM, damien thiriet via ntg-context wrote:
> Hi,
>
>
> I have two question regarding OBSD binaries:
>
> 1)
> the building farm holds two binaries: current -stable version (or
> -release?) and the previous version.
> Since upgrading OBSD with sysupgrade is very easy, but AFAIU works only
> to upgrade from version (n-1) to n where n is current relase number, I
> wonder if it wouldn't easier to maintain binaries only for the current
> version: keeping the OS up to date is strongly recommended.
Wasn't it you who actually suggested to have the two versions?
> https://www.openbsd.org/faq/faq5.html#Flavors
>
> This might ease OBSD binaries management.
> What do other OBSD users think about it?
>
> 2) AFAIU, sources are now available for downloading.
> I understand it would be possible to make a package build for my system,
> so that I can upgrade OBSD without having to wait for the next binaries
> upload.
> * binaries are quite small, so they should compile quite quickly. Am I
> right?
> * I believe Mojca has already a compiling script. Where can I find it?
> * which adress should I point to fetch the sources for compilation?
the sources are in the distribution as is build.sh
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2022-11-04 9:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 8:24 damien thiriet via ntg-context
2022-11-04 9:06 ` Hans Hagen via ntg-context [this message]
2022-11-09 18:45 damien thiriet via ntg-context
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48939a61-ec6e-ed98-5aee-78bde80ff80f@xs4all.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@xs4all.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).