On Tue, Dec 11, 2018 at 03:01:06PM -0800, Gary E. Miller via devel wrote:
>
> I am unaware of any other Python libraries not in the base Python that
> NTPsec uses. For some reason *BSD don't like curses.
>
> You know any other used Python packages not in the base Python?
What about the "gps"
On Mon, Dec 17, 2018 at 01:55:16PM -0800, Hal Murray via devel wrote:
>
> James Browning said:
> > IIRC OpenSUSE does the same thing. I don't recall seeing a streak of red
> > build fail indicators though. Possibly because I seem to remember adding it
> > to the CI file.
James Browning said:
> IIRC OpenSUSE does the same thing. I don't recall seeing a streak of red
> build fail indicators though. Possibly because I seem to remember adding it
> to the CI file.
Thanks.
Are you in a position to test buildprep on OpenSUSE and/or friends? It looks
to me like it
On 12/11/18 1:37 PM, Gary E. Miller via devel wrote:
> First we need to start including better dependency info for different
> distros in the INSTALL file. Without that we don't know which packages
> to look at.
I wasn't aware of, until this thread, or had forgotten the ntpmon curses
Yo Hal!
On Tue, 11 Dec 2018 14:45:11 -0800
Hal Murray via devel wrote:
> > Gary E. Miller via devel :
> >> ntpmon should not required, but very strongly encouraged. So test
> >> for pythong curses, complain loudly when not found, but do not
> >> fail at that point.
>
> > +1
>
> Why do
> Gary E. Miller via devel :
>> ntpmon should not required, but very strongly encouraged. So test for
>> pythong curses, complain loudly when not found, but do not fail at that
>> point.
> +1
Why do you say that?
I don't care what the answer is. That seems like the sort of code you like
Yo Hal!
On Tue, 11 Dec 2018 03:00:20 -0800
Hal Murray via devel wrote:
> Should we rip out the test for python curses? That makes curses a
> requirement for a clean build.
If you rip out the test for curses, then you have to rip out ntpmon.
ntpmon should not required, but very strongly
On Tue, Dec 11, 2018, 3:00 AM Hal Murray via devel
> I don't know why I didn't figure this out ages ago, but ...
>
> It's in a separate package rather than the main python package.
>
> Should we rip out the test for python curses? That makes curses a
> requirement
> for a clean build.
>
> Or are
I don't know why I didn't figure this out ages ago, but ...
It's in a separate package rather than the main python package.
Should we rip out the test for python curses? That makes curses a requirement
for a clean build.
Or are there other similar things that might be optional? Should we
