Date: Wed, 25 Jun 2014 09:09:30 -0700 From: Warner Losh <imp@bsdimp.com> To: Baptiste Daroussin <bapt@FreeBSD.org> Cc: arch@FreeBSD.org, hackers@FreeBSD.org, "Matthew D. Fuller" <fullermd@over-yonder.net> Subject: Re: [CFR] Remove texinfo from base Message-ID: <E6402E7B-7490-406A-B973-4642D590F040@bsdimp.com> In-Reply-To: <20140625154758.GD23976@ivaldir.etoilebsd.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>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] 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 [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJTqvQ6AAoJEGwc0Sh9sBEAX6EQAKIhsFfHmnnNxZgoWB+GFIuF IJwVq2TSL1+InLufCcQcxsWvHfqDEcR5oDTgdjMTdrf9S1PTiMtHYP8TYoPMivjN U1iWtJfDdMSEQkk5t449TU+m4q7YqV9FZh2rx2MSXQ2E8fRbX2HhUl1p+PZPcEwF coPV2caY04LYhgyoE08a/S7nsQ1jm1hO1KrWjzaftr7CPWuvxjmZEQv4sunyU9kB MhrE5m0rV31n40sAuayduzfRWEesbwwLLtM5FK167nuX0JAW5GSEKeKt16ar9eQR nHV/yHWPc8yVlm/cY5NGp20BW4TxAmRaKoi4Yx3JYg8jyKCHP+Ahery65j2I5Eht y1qQta/StmD2hXNsdVzQAD72K3829zuadN4fdyvxDhXW3ckglMoCiPfUtTt82Cvk xBaHb1pvKIbKfFx61XiVVwzWtYClY6VB7+jF6RjHTLQo3mmHfFgvdTPJMPi8Cmgg b2uB+9lEpDYG5O0YdwLlwG2m5FufU/BmTtDEcC4BMok+vL8q3mqU8YftHX7pLdQE l+tvXUdm5w63Kp0DnpSh11AsVtPcOSQEqXuoq5cxIwBwp9Fh3lPntgEzKze552l2 1EBGR2+2ieCbekqggcHUsa32k4U+iZ2f3Mf4oRFyQkNp18exAXPbBOE9S6Ce6nkd 1BhFyGNJBRbsf7S9D8sj =D/gg -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E6402E7B-7490-406A-B973-4642D590F040>