Re: Automated OS builds?

2020-01-06 Thread Stuart Henderson 
On 2020-01-05, Marc Espie  wrote:
> On Sun, Jan 05, 2020 at 06:08:55PM +, Paul Suh wrote:
>> On Jan 5, 2020, at 12:43 PM, Morten Gade Liebach  wrote:
>> > 
>> > Read release(8), then write a script runs through the described process.
>> 
>> I can do that, and will if I have to, but if someone has already done it or 
>> has a base to start from that would be better. (I’ve been building OpenBSD 
>> releases that way since 3.2? 3.3? Something like that.) 
>
> There are so many specifics to how each person configures his system and 
> curates his local changes,
> it's hard to give a "one size fits all".

Exactly. But don't bother trying to look for changes before deciding to
update the source tree from the repo - just do the 'cvs up' and check
the output to see if anything changed.
>

Re: Automated OS builds?

2020-01-05 Thread Marc Espie 
On Sun, Jan 05, 2020 at 06:08:55PM +, Paul Suh wrote:
> On Jan 5, 2020, at 12:43 PM, Morten Gade Liebach  wrote:
> > 
> > Read release(8), then write a script runs through the described process.
> 
> I can do that, and will if I have to, but if someone has already done it or 
> has a base to start from that would be better. (I’ve been building OpenBSD 
> releases that way since 3.2? 3.3? Something like that.) 

There are so many specifics to how each person configures his system and 
curates his local changes,
it's hard to give a "one size fits all".

(the complementary page for ports is bulk(8) btw
which goes to great length explaining the problems
you might encounter due to the size of the ports tree)

Re: Automated OS builds?

2020-01-05 Thread Paul Suh 
On Jan 5, 2020, at 12:43 PM, Morten Gade Liebach  wrote:
> 
> Read release(8), then write a script runs through the described process.

I can do that, and will if I have to, but if someone has already done it or has 
a base to start from that would be better. (I’ve been building OpenBSD releases 
that way since 3.2? 3.3? Something like that.) 


—Paul

Re: Automated OS builds?

2020-01-05 Thread Morten Gade Liebach 
Read release(8), then write a script runs through the described process.


--
Morten Gade Liebach ★ https://m.lieba.ch/

‐‐‐ Original Message ‐‐‐
On Sunday, January 5, 2020 5:29 PM, Paul Suh  wrote:

> Folks,
>
> My DuckDuckGo-fu seems to be weak right now.
>
> Is there a set of automated scripts somewhere that:
>
> 1.  Checks anoncvs*.*.openbsd.org:/cvs for updates to the patch branch source 
> tree
> 2.  Checks them out
> 3.  Builds them
> 4.  Builds a release
>
> Then notifies me when this has happened?
>
> I’m looking to follow the patch branch but since I’m using flashrd I 
> can’t use syspatch on my production systems. (Yes I know I’m not asking for 
> help with flashrd, but with an automated build system for the base system.)
>
> I can hack something like this together but I’m kinda surprised that I 
> can’t find something that someone else has already done. Or maybe I’m just 
> bad with search engines.
>
> —Paul
>

Automated OS builds?

2020-01-05 Thread Paul Suh 
Folks,

My DuckDuckGo-fu seems to be weak right now. 

Is there a set of automated scripts somewhere that: 

1) Checks anoncvs*.*.openbsd.org:/cvs for updates to the patch branch source 
tree
2) Checks them out
3) Builds them
4) Builds a release

Then notifies me when this has happened? 

I’m looking to follow the patch branch but since I’m using flashrd I can’t use 
syspatch on my production systems. (Yes I know I’m not asking for help with 
flashrd, but with an automated build system for the base system.) 

I can hack something like this together but I’m kinda surprised that I can’t 
find something that someone else has already done. Or maybe I’m just bad with 
search engines. 


—Paul