I do not think that this is completely accurate. Sometimes people will not listen, but sometimes they will.
-- Raul On Tue, Aug 2, 2016 at 5:06 PM, dsendkowski <dsendkow...@gmail.com> wrote: > I really don't know why you, Theo, burn so much energy on such discussions. It doesn't make any sense. If someone wants to complain they will anyway. No matter what you say they will keep complaining. It is impossible to fulfill everybody's requirements so if someone is not satisfied than it is their problem, not yours. > PSThanks for OpenBSD. You guys are doing great job. > > > > > -------- Original message --------From: Theo de Raadt <dera...@openbsd.org> Date: 8/2/16 21:13 (GMT+01:00) To: Sonic <sonicsm...@gmail.com> Cc: bytevolc...@safe-mail.net, Marc Espie <es...@nerim.net>, misc <misc@openbsd.org> Subject: Re: tmpfs >> On Tue, Aug 2, 2016 at 9:42 AM, Theo de Raadt <dera...@openbsd.org> wrote: >> > Whoa. You haven't read the first paragraph of current.html, let me >> > include it here: >> > >> > Active OpenBSD development is known as the -current branch. These >> > sources are frequently compiled into releases known as >> > snapshots. Active development sometimes pushes aggressive changes, and >> > complications can arise when building the latest code from a previous >> > point in time. Some of the shortcuts for getting over these hurdles >> > are explained on this page. In general, it's far better to use the >> > OpenBSD upgrade procedure with a newer snapshot, as developers will >> > have gone through the trouble for you already. >> > >> > That purpose of the page is to help people "make build" through the >> > most disruptive changes. >> > >> > You seem to believe it is for a different purpose -- to alert about removal >> > of subsystems which are not critical for building through snapshots. >> >> Yes, and admittedly my mistake. Although I have found current.html to >> be quite valuable beyond getting past "make build", so in my defense >> it's an easy mistake to make. >> Take the last 4 entries. for example: >> 2016/05/28 - iwm(4) needs new firmware >> 2016/06/30 - doas.conf adjustment >> 2016/07/13 - [packages] OpenSMTPD-extras filters removal >> 2016/08/01 - new mandoc.db(5) format >> >> Certainly all useful, but which of these, if any, would hamper a "make >> build"? Possibly the doas.conf, but at least it will print a warning. >> Is it possible that limiting the contents to just those items that >> would prevent a "make build" might be a bit too restrictive (since it >> really hasn't been done in the past)? > > I see you have selected only the parts of my reply which suit you. > > The rest of my reply clearly stated we don't have people to do the > work you want. > >> I doubt I'm the only non-developer who counts on that file to help >> me keep from going astray in so many possible ways when attempting >> to remain -current. > > You count on it? The first paragraph tells you not to count on it! > > Basically you have no preperation, except counting on us doing > something we say we won't do?
