* Torsten Veller ml...@veller.net:
The perl-module.eclass must be updated to support EAPI=3 [1] and
a new eclass will be added which does contain some (more or less) useful
stand-alone functions split from the old perl-module.eclass without
exporting phase functions.
Somehow I was sleeping:
* James Cloos cl...@jhcloos.com:
TV == Torsten Veller ml...@veller.net writes:
TV There was a reason why the man-pages were removed: I think it was
TV collisions protection and perl people use `perldoc` anyway.
Perl people -- I'm one -- use man(1); given the differences in
usefulness, I
Hi,
Torsten Veller ml...@veller.net:
find ${S} -type f -name ._* -print0 | while read -rd ''
f ; do einfo Removing AppleDouble encoded Macintosh file: ${f#${S}/}
rm -f ${f}
f=${f#${S}/}
# f=${f//\//\/}
# f=${f//\./\.}
#
On 12-04-2010 10:07:54 +0200, Christian Faulhammer wrote:
if [[ -d ${D}/${VENDOR_LIB} ]] ; then
Haven't checked, but quotes not needed?
it's within [[ ]], so no.
--
Fabian Groffen
Gentoo on a different level
MG == Michał Górny gen...@mgorny.alt.pl writes:
MG I prefer perldoc over man. And I cannot imagine why anyone would prefer
MG keeping two copies of the same docs if generating one from another
MG takes less than a second.
It takes more than a mere second, and man(1), man.el, woman.el and the
D == Duncan 1i5t5.dun...@cox.net writes:
D While you're correct in the ordinary case, keep in mind that this is perl
D developer docs we're talking about here -- not ordinary user documentation.
Developer docs *are* ordinary user documentation. Section 3 is perhaps
the most used section of
TV == Torsten Veller ml...@veller.net writes:
TV * James Cloos cl...@jhcloos.com:
One change the perl eclasses require is elimination of the code which
deletes the man pages.
Deleting the man pages is /extremely/ rude and should not occur.
TV There was a reason why the man-pages were
MH == Michael Higgins li...@evolone.org writes:
MH Yep. Why have a man page for a perl module? OTOH, if there is something
MH that goes in /usr/bin, it should get a man page if there is one. But
MH not for the modules themselves -- that's not needed at all.
Because man(1) works better than the
James Cloos posted on Tue, 06 Apr 2010 10:27:36 -0400 as excerpted:
MH == Michael Higgins li...@evolone.org writes:
MH Yep. Why have a man page for a perl module? OTOH, if there is
something MH that goes in /usr/bin, it should get a man page if there
is one. But MH not for the modules
On Tue, 06 Apr 2010 10:25:27 -0400
James Cloos cl...@jhcloos.com wrote:
Perl people -- I'm one -- use man(1); given the differences in
usefulness, I cannot imagine why anyone would prefer perldoc(1)
over man(1).
I prefer perldoc over man. And I cannot imagine why anyone would prefer
keeping
On Sat, 3 Apr 2010 12:33:48 +0200
Torsten Veller ml...@veller.net wrote:
perl people use `perldoc` anyway.
Yep. Why have a man page for a perl module? OTOH, if there is something
that goes in /usr/bin, it should get a man page if there is one. But
not for the modules themselves -- that's not
* Alec Warner anta...@gentoo.org:
It is obvious what many of the functions do (I can read shell, yay!)
but it is not obvious to me why they exist or why I would want to call
them. Why do I want to delete AppleDouble files? What are dual-life
scripts and why do I want to symlink them? Why
* James Cloos cl...@jhcloos.com:
One change the perl eclasses require is elimination of the code which
deletes the man pages.
Deleting the man pages is /extremely/ rude and should not occur.
There was a reason why the man-pages were removed: I think it was
collisions protection and perl
On 04/01/2010 07:41 PM, James Cloos wrote:
And given that portage inappropriately ignores a fixed eclass in the
OVERlay, that means that every time one syncs one must re-patch the
offending eclasses.
If you want all ebuilds to use eclasses from a given overlay (if available)
instead of the
14 matches
Mail list logo
