Date: Fri, 11 Jul 2014 02:08:56 +0200 From: Baptiste Daroussin <bapt@FreeBSD.org> To: "John D. Hendrickson and Sara Darnell" <johnandsara2@cox.net> Cc: hackers@FreeBSD.org, "Matthew D. Fuller" <fullermd@over-yonder.net> Subject: Re: [CFR] Remove texinfo from base Message-ID: <20140711000856.GH93051@ivaldir.etoilebsd.net> In-Reply-To: <53BF28D1.8010604@cox.net> References: <20140625103107.GB23976@ivaldir.etoilebsd.net> <20140625104540.GE86779@over-yonder.net> <20140625105209.GC23976@ivaldir.etoilebsd.net> <20140625110049.GF86779@over-yonder.net> <40EA1066-4776-4B2E-988A-9900BB842862@bsdimp.com> <20140625154758.GD23976@ivaldir.etoilebsd.net> <Jg9k1o00f2X408g01g9lQP> <53BF28D1.8010604@cox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Thu, Jul 10, 2014 at 07:59:13PM -0400, John D. Hendrickson and Sara Darnell wrote: > Warner Losh wrote: > > On Jun 25, 2014, at 8:47 AM, Baptiste Daroussin <bapt@FreeBSD.org> wrote: > > > >> On Wed, Jun 25, 2014 at 08:20:41AM -0700, Warner Losh wrote: > >>> On Jun 25, 2014, at 4:00 AM, Matthew D. Fuller <fullermd@over-yonder.net> wrote: > >>> > >>>> On Wed, Jun 25, 2014 at 12:52:10PM +0200 I heard the voice of > >>>> Baptiste Daroussin, and lo! it spake thus: > >>>>> I have just committed the support for this in ports, anyway breakage > >>>>> should be reported, right now it seems fine on my exp-run > >>>> Oh, yes. Sorry, I did phrase that poorly. This shouldn't _break_ > >>>> anything, but I suspect it will uncover existing-but-hidden breakage. > >>>> > >>>> Which is good. But does merit awareness that "hey, this will probably > >>>> happen somewhere, so know this is a place to look when a build > >>>> breaks". > >>> I know it will break certain nanobsd configurations that build ports because > >>> dependencies there (at least for the ones I’ve done) aren’t well handled. So > >>> I agree that this patch is missing, at the very least, an UPDATING entry and > >>> a __FreeBSD_version bump. > >> If you build a port that needs texinfo the port framework will do what it needs > > > > Except in environments that don’t do dependencies quite right, or where only a subset > > of ports tree has been imported and texinfo isn’t part of that… But people with them > > usually know, which is why UPDATING is needed. That’s all. There’s nothing else for you > > to do. > > > > Warner > > i a few times heard there was and IS a long standing stand-off between > info(1) and man(1) because man was copyright at least in part and > further reasons that were not discussed. > > remove the ability to look at existing info pages of say m4.info why? We do not have m4.info pages and so for a while :) in base because we do not have GNU m4 in base. > > replace it with what ? > > i'm impartial. i like both, made a manpage maker, would like a good > info editor haven't come across yet. coolman in nonfree, tkinfo is > free. debian won't allow manpages on it's user groups > > do you know anything about this standoff between the online page and > online manual systems ? > > are you saying that whatever microbsd prefers should be the base of bsd ? > > is microbsd used by Apple or something ? [...] skipping the above because I don't understand how it comes to the conversation. If you want to read info pages just install texinfo from ports or add WITH_INFO in your src.conf. regards, Bapt [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlO/KxgACgkQ8kTtMUmk6Ez/JQCeM/A+NdQ4C59Chwdw9l/q177i E+oAnRBdt+bCnhWUTYuQrDPdyVxYu25/ =ODPr -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140711000856.GH93051>