Date: Mon, 08 Sep 2014 16:37:01 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 193183] [STAGE] net/beacon: Request MAINTAINERship, pkg-descr cleanup Message-ID: <bug-193183-13-MTYd7xtNT7@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-193183-13@https.bugs.freebsd.org/bugzilla/> References: <bug-193183-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193183 --- Comment #29 from C Hutchinson <portmaster@bsdforge.com> --- (In reply to John Marino from comment #28) > I did some research. > compress-man target is essentially an internal target. It can be > overridden. Your definition of MANCOMPRESSED here did nothing. > > I think if you had: > compress-man: > YOUR_MAMA_IS=UGLY > > it would have the same effect. (Try it!) > It basically blocked the default "compress-man" target from executing. > by the way, anything after a target has to be indented. I'm not sure why > make(1) didn't scream at you. Ahh. So this (compress-man:) is an [unintended] _feature_. :) Meaning; If I use compress-man: MANCOMPRESSED= no man(1) && perldoc(1) pages are left un-gzipped && copied to their intended destination(s) -- really, I tried it. UNindented. BUT if I omit that block, the man(1) && perldoc(1) pages, are packed in their intended destination(s) -- really, I tried it. :) In both cases, the files DO get installed. Either gzipped | UNgzipped; depending upon the whether MANCOMPRESSED is defined, or not. I have no explanation for it all. I just only discovered it. It might be interesting to take the time to find, and unwind the logic that even [still] permits this. But my plate [as you've already discovered] is nearly overflowing, as it is. :) P.S. _love_ the YOUR_MAMA_IS=UGLY example. :) Good thing I'm not sensitive, that way. ;) > > > > It's a perlbrew||cpanminus -ism. I cobbled a Perl script to clean up this > > very thing. But since it's empty (of documentation), it's harmless. So > > I didn't think it worth bothering with. If it bothers you. I can deal > > with the Module' extra entry, and bump it's version, to reflect that. > > But IMHO, in the here-and-now. It doesn't really seem necessary. > > Personally, I'm glad that this showed up. As I gained some useful > > information, where man(1) && perldoc(1) pages are concerned, when > > dealing with ports. > > I don't really follow. > If you don't install this file, does anything break or malfunction? No. No issue, at all. It's [supposed] to only be appended to, as|if needed. Go ahead, and issue a perldoc perllocal. You may, or may not get something. Depending if there's any contents|exists, in your [Perl] install(s). Thanks, John. --Chris -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-193183-13-MTYd7xtNT7>