From: Torsten Veller <ml-en@veller.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: perl eclass review - EAPI=3 + new helper eclass
Date: Sat, 3 Apr 2010 12:33:57 +0200 [thread overview]
Message-ID: <20100403103357.GA6545@veller.net> (raw)
In-Reply-To: <b41005391003300848t4a7d6e0cya39199fc1eb95a18@mail.gmail.com>
* Alec Warner <antarus@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 would I want to delete
> packfiles? Some documentation would be nice h ere.
Absolutely. The perl-team already has a bug for it (#259815).
Perl eclass changes are tracked in bug #239510.
But I don't think missing documentation is a stopper here. Most of it
is copied from perl-modules.eclass.
- AppleDouble (name reported by `file`)
268497 [perl@gentoo.org] - Remove ._* files in perl-module_src_prepare
273104 [dev-portage@gentoo.org] - New QA check: installed OSX fork files (if I got the name right)
- dual-life scripts
scripts installed by dual-life packages (part of dev-lang/perl and
also stand-alone in perl-core/). Only relevant for perl-core/
packages.
- .packlist
something like CONTENTS.
[---=| TOFU protection by t-prot: 143 lines snipped |=---]
next prev parent reply other threads:[~2010-04-03 10:34 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 11:11 [gentoo-dev] perl eclass review - EAPI=3 + new helper eclass Torsten Veller
2010-03-30 15:48 ` Alec Warner
2010-04-03 10:33 ` Torsten Veller [this message]
2010-04-01 23:41 ` James Cloos
2010-04-02 0:12 ` [gentoo-dev] " Jonathan Callen
2010-04-02 0:14 ` [gentoo-dev] " Zac Medico
2010-04-02 0:17 ` Brian Harring
2010-04-02 0:25 ` Zac Medico
2010-04-06 14:22 ` James Cloos
2010-04-06 18:39 ` Zac Medico
2010-04-12 17:17 ` James Cloos
2010-04-12 17:30 ` James Cloos
2010-04-12 18:00 ` Brian Harring
2010-04-12 22:55 ` Zac Medico
2010-04-16 20:00 ` James Cloos
2010-04-12 22:47 ` Zac Medico
2010-04-16 20:23 ` James Cloos
2010-04-16 20:28 ` Ciaran McCreesh
2010-04-17 3:30 ` Steev Klimaszewski
2010-04-17 7:13 ` Ciaran McCreesh
2010-04-18 3:28 ` James Cloos
2010-04-18 7:45 ` Ciaran McCreesh
2010-04-19 20:59 ` James Cloos
2010-04-19 21:46 ` Harald van Dijk
2010-04-23 15:14 ` James Cloos
2010-04-25 6:16 ` Zac Medico
2010-04-03 10:33 ` [gentoo-dev] " Torsten Veller
2010-04-04 8:25 ` Michael Higgins
2010-04-06 14:27 ` James Cloos
2010-04-06 14:52 ` Duncan
2010-04-10 0:40 ` James Cloos
2010-04-06 14:25 ` James Cloos
2010-04-06 16:00 ` Michał Górny
2010-04-10 0:34 ` James Cloos
2010-04-17 20:07 ` Torsten Veller
2010-04-12 8:07 ` Christian Faulhammer
2010-04-12 9:03 ` Fabian Groffen
2010-04-20 6:49 ` Torsten Veller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100403103357.GA6545@veller.net \
--to=ml-en@veller.net \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox