Ingo Schwarze wrote:
[…]
>
> > but it's so damn frustrating when I need to look
> > up some of the differences.
>
> On a build slave, i guess you do have the disk space to simply
> install all the -doc packages for the packages you are using?
> Sure, it's one additional step at install time,
Hi Dumitru,
Dumitru Moldovan wrote on Tue, Oct 31, 2017 at 10:58:25AM +0200:
> On 30.10.2017 00:32, Ingo Schwarze wrote:
>> Cag wrote on Sun, Oct 29, 2017 at 09:49:49PM +:
>>> man/info pages, pdf/html docs - in -doc;
>> Over my dead body. Software without documentation is completely
>> usel
On 30.10.2017 00:32, Ingo Schwarze wrote:
> Hi,
>
> Cag wrote on Sun, Oct 29, 2017 at 09:49:49PM +:
>
>
>> man/info pages, pdf/html docs - in -doc;
>
> Over my dead body. Software without documentation is completely
> useless, almost a crime. Docs must always be available, even on
> a tin
Patch:
add "--disable-avahi --disable-dbus" to configure.
I hope the package maintainers will consider the opportunity to make their task
easier, by applying the above and thus removing a shitload of dependencies that
are both functionally unnecessary and a security hazard.
End-of-thread.
Sen
Hi,
gwes wrote on Mon, Oct 30, 2017 at 01:43:03AM -0400:
> The last time AVAHI got installed on one of my systems
> the installer started it immediately.
> Avahi then proceeded to scribble on that system's
> network configuration and confuse other systems on
> that subnet.
That doesn't sound lik
Hi,
Rupert Gallagher wrote on Mon, Oct 30, 2017 at 06:11:45AM -0400:
> Ingo, we must not install 100MB of unwanted optional software.
> Since when OpenBSD joined the bandwagon of bloatware?
Since 1995.
Sure, OpenBSD tends to avoid installing stuff that is never needed,
but avoiding to install s
Does ports@ no longer exist?
>
> On Oct 30, 2017 at 5:59 AM,wrote:
>
>
> On Mon, Oct 30, 2017 at 06:36:38AM -0400, Rupert Gallagher wrote: > The
> openbsd decision to make cups package dependent from avahi is > opaque.
> Where can we read this decision? What is
On Mon, Oct 30, 2017 at 06:36:38AM -0400, Rupert Gallagher wrote:
> The openbsd decision to make cups package dependent from avahi is
> opaque. Where can we read this decision? What is the evidence that
> supported it? Is this evidence still relevant? Why, oh why, the
> package maintainer(s) of cup
On Mon, Oct 30, 2017 at 06:11:45AM -0400, Rupert Gallagher wrote:
> Ingo, we must not install 100MB of unwanted optional software.
> Since when OpenBSD joined the bandwagon of bloatware?
It's happened ever since you chose not to do anything about it.
It's your choice. If you really need to get ri
noth --> both
Sent from ProtonMail Mobile
On Mon, Oct 30, 2017 at 11:36 AM, Rupert Gallagher wrote:
>> being critical of decisions made > You don't get to make the decisions,
>> since you aren't doing the work I can do the work. As a matter of fact, I
>> build my servers from scratch, from th
+1
Sent from ProtonMail Mobile
On Mon, Oct 30, 2017 at 6:43 AM, gwes wrote:
> The last time AVAHI got installed on one of my systems the installer started
> it immediately. Avahi then proceeded to scribble on that system's network
> configuration and confuse other systems on that subnet. I wo
> being critical of decisions made
> You don't get to make the decisions, since you aren't doing the work
I can do the work. As a matter of fact, I build my servers from scratch, from
the firmware all the way up to the automatic configuration of clients. It is
hell, but I get what I need, and
Ingo, we must not install 100MB of unwanted optional software. Since when
OpenBSD joined the bandwagon of bloatware?
Sent from ProtonMail Mobile
On Sun, Oct 29, 2017 at 9:26 PM, Ingo Schwarze wrote:
> Hi, gwes wrote on Sun, Oct 29, 2017 at 03:40:48PM -0400: > On 10/26/17 07:24,
> Rupert Galla
The last time AVAHI got installed on one of my systems
the installer started it immediately.
Avahi then proceeded to scribble on that system's
network configuration and confuse other systems on
that subnet.
I would assert that Avahi should be either (a)
not automatically started when installed or
I don't like the idea of splitting packages, but I get weirded out when
ghostscript (which DOES have a no_x11 variant) winds up pulling in dbus.
I guess there's no escaping freedesktop.org.
khm
Hi Cag,
Cag wrote on Sun, Oct 29, 2017 at 10:51:29PM +:
> Ingo Schwarze wrote:
>> No. OpenBSD is a developer-oriented system, so headers are an
>> integral part of the installation. Installing them must not be
>> optional, or it will cause nothing but needless confusion as soon
>> as peopl
On Sun, Oct 29 2017, Ingo Schwarze wrote:
[...]
>> /usr/local/share/locale files - in -lang;
>
> In most cases useless on OpenBSD, most of that stuff isn't used
> in the first place.
Most of what can be found in /usr/local/share/locale are LC_MESSAGES
files handled by gettext, they are actuall
> > No. OpenBSD is a developer-oriented system, so headers are an
> > integral part of the installation. Installing them must not be
> > optional, or it will cause nothing but needless confusion as soon
> > as people actually start using what they installed.
>
> And what if someone wants to buil
Ingo Schwarze wrote:
> No. OpenBSD is a developer-oriented system, so headers are an
> integral part of the installation. Installing them must not be
> optional, or it will cause nothing but needless confusion as soon
> as people actually start using what they installed.
And what if someone wan
> > So basically you are saying the ports developers, who have worked very
> > hard, haven't built things exactly the way you want.
> > Did I get that right?
>
> Nobody apparently cared about it (neither do I really). It's an idea to
> be discussed (or not), not a proposal to have an answer right
> So basically you are saying the ports developers, who have worked very
> hard, haven't built things exactly the way you want.
> Did I get that right?
Nobody apparently cared about it (neither do I really). It's an idea to
be discussed (or not), not a proposal to have an answer right now.
> By t
Hi,
Cag wrote on Sun, Oct 29, 2017 at 09:49:49PM +:
> headers and such - in -dev;
No. OpenBSD is a developer-oriented system, so headers are an
integral part of the installation. Installing them must not be
optional, or it will cause nothing but needless confusion as soon
as people actuall
> > Build time of cups isn't really an issue. But the dependency chain
> > around cups is already very delicate, and anything involving optional
> > dependencies for a library gets *really* awkward further down the chain.
>
> How about package splitting? cups doesn't require avahi binaries or XML
Stuart Henderson wrote:
> Build time of cups isn't really an issue. But the dependency chain
> around cups is already very delicate, and anything involving optional
> dependencies for a library gets *really* awkward further down the chain.
How about package splitting? cups doesn't require avahi
On 2017-10-29, gwes wrote:
> When this works you should probably work with the ports
> group to make this version available. They may not accept
> it because compiling another version of cups on their
> build systems would take too long.
Build time of cups isn't really an issue. But the dependenc
Hi,
gwes wrote on Sun, Oct 29, 2017 at 03:40:48PM -0400:
> On 10/26/17 07:24, Rupert Gallagher wrote:
>> If you have a server with limited resources and without X11,
>> you cannot install the present cups package.
I can't comment on CUPS and avahi in particular, but yes, in general,
X libraries
On 10/26/17 07:24, Rupert Gallagher wrote:
It is well known that cups does not need avahi.
Avahi is an option, it requires dbus, which requires X11. If you have a server
with limited resources and without X11, you cannot install the present cups
package.
Please remove cups's dependency on av
It is well known that cups does not need avahi.
Avahi is an option, it requires dbus, which requires X11. If you have a server
with limited resources and without X11, you cannot install the present cups
package.
Please remove cups's dependency on avahi.
28 matches
Mail list logo
