OK.

But OpenBSD also has "OPENBSD_5_4_BASE" which is what I understood as "primary 
snapshot release for 5.4" and "OPENBSD_5_4" which I understand as "5.4 release 
plus required (security only ?) patches". I thought, maybe opensmtpd would also 
be updated in "OPENBSD_5_4" and not only in "HEAD".

From what I see, OpenSMTPD as shipped with OpenBSD 5.4 is tagged 5.4.
Last snapshot I grabbed (mostly for Bug #333 correction) is tagged 201310281422.
It's not straight forward to deal with but since one knows when OpenBSD 5.4 
start shipping... :)

So since OpenBSD X.X is released, the only way to get new featured or bug 
corrected OpenSMTPD is either use OpenBSD "HEAD" or OpenSMTPD snapshots, right?

Le 8 nov. 2013 à 18:16, Bryan Vyhmeister <[email protected]> a écrit :

> The version in archives is definitely newer. A release of OpenBSD is tagged 
> and the tree frozen for that release months back in order for CD duplication 
> and so forth. That's why archives has a much newer version. It is regularly 
> synced to -current as you noticed and I believe 5.4 has OpenSMTPD version 
> 5.3.x. 
> 
> Bryan
> 
> ---
> Bryan Vyhmeister
> Sent from my iPhone
> 
>> On Nov 8, 2013, at 9:11, Joel Carnat <[email protected]> wrote:
>> 
>> Hi,
>> 
>> I was looking at opensmtpd in brand new openbsd 5.4 and it seems not to be 
>> as fresh as the one in /archives/.
>> I also had a look at the Web CVS of OpenBSD and, as far as I understood it, 
>> opensmtpd seem to not be synced in the "release" tree but rather in the 
>> "current" one.
>> 
>> Am I wrong or do one have to rather use /archives/ to be able to get the 
>> required latest fixes on opensmtpd ?
>> 
>> Thanks.
>> -- 
>> You received this mail because you are subscribed to [email protected]
>> To unsubscribe, send a mail to: [email protected]
>> 
> 
> --
> You received this mail because you are subscribed to [email protected]
> To unsubscribe, send a mail to: [email protected]
> 


--
You received this mail because you are subscribed to [email protected]
To unsubscribe, send a mail to: [email protected]

Reply via email to