is going to publish this in a module:
"succeed", rather than "succeeded".
Cheers
Smylers
iscussion seems no longer
specific to Perl QA; perhaps the perl-qa list doesn't need to included
on Perl-wide logo discussions?
Smylers
--
http://twitter.com/Smylers2
David Golden writes:
> On Fri, May 15, 2009 at 12:11 PM, Smylers wrote:
>
> > That Perl has this QA thing which tells you which platforms a
> > module will work on but that doesn't actually mean it'll install
> > only adds to external perceptions of Perl
-- any others?) is in a directory that
isn't in PMLIBDIRS?
Smylers
tests should be run from the parent
directory:
http://www.nntp.perl.org/group/perl.qa/2009/05/msg12215.html
Any thoughts?
Smylers
Andy Armstrong writes:
> On 11 Feb 2009, at 13:50, Smylers wrote: O
>
> > TAP::Struct?
>
> +0 - in the sense that it's fine by me - but I can still imagine a
> better noun even if I can't think what it is :)
+1 to Andy's comment on my suggestion!
Smylers
Steffen Schwigon writes:
> For this purpose I need a reliable data structure that containes
> parsed TAP.
TAP::Struct?
Yeah, I know "struct" is a C-ism, but it's quite well known (it has a
Wikipedia page!) and at least makes the point it's structured data
rather than just "data".
Smylers
Michael G Schwern writes:
> Smylers wrote:
>
> > > I have lying around a prototype for the CPAN shell to warn the user
> > > when they run it as root and offer to reconfigure itself to only su
> > > for the install. That would help plug the hole.
> >
&
Michael G Schwern writes:
> Smylers wrote:
>
> > you're talking about Cpan being something morally equivalent to a
> > common carrier, rather than an actual common carrier in the legal
> > sense?
>
> Yes, because we are not lawyers I don't even wa
ide them and get involved in their business,
> for whatever reason, you are no longer a common carrier. This is a
> whole different ball game.
Indeed. But if Cpan is only _like_ a common carrier, then it never
actually had common carrier protection in law in the first place -- so
surely it can't lose it?
Smylers
ets ...
Rejecting certain undesirable uploads meeting well-defined criteria is a
long way from modifying stuff in other people's names.
Smylers
So umask would be ignored for Andreas above because he un-tar-ed as root
(and I'm guessing you tried it as you, thereby not triggering the
behaviour).
Requiring root privs for the last step of installation is common, so I
guess it's fairly common for some people to do all the steps as root
(however inadvisable that is).
Smylers
David Cantrell writes:
> Smylers wrote:
>
> > It sounds scary to me. If I'm just installing a Perl module from
> > Cpan on a newly installed OS, which happens to still have default DB
> > connection permissions, I wouldn't expect the module's tests to
Greg Sabino Mullane writes:
> > ... I suppose it could also be somewhat easy to try out a few series
> > of basic/default credentials on localhost for engines like MySQL and
> > Postgres, and try to setup a test database from there.
>
> That sounds more interesting.
It sounds scary to me. If I'
ers of the group can write to
them, as intended.
Whereas a umask of 0022 would leave the files not group-writeable, so
you would have to specifically chmod them each time. That's irritating.
Having 0002 is more convenient, and, so long as your default group is
one with only you in it, not a security risk.
Smylers
consistently
return 3, and you wish to be alerted if it suddenly starts returning 4,
then surely you can do that with a non-TODO test which checks for its
being 3?
Then, when the TODO is done you can remove that test entirely (while
also removing the TODO marker from the check for 1)?
Smylers
a die
handler into a library, which then broke something which used that
library. The code was completely under our control; we were able to fix
it.
But it'd've been good to have a test; perhaps that would've stopped the
die handler being committed like that in the first place.
Smylers
get used together. You can reduce the risk of name clashes by
starting all your keys with a standard prefix or your organization or
project name (or something else likely to be unique).
Smylers
dora or Ubuntu user is wanting to check that upgrading the
OS hasn't caused any test regressions, it's likely that at least some of
the existing Perl modules were installed as RPMs or Debian packages, not
by CPAN.pm from tarballs.
Smylers
nct private keys? I'm not sure that's advantageous;
picking a single way of denotating privacy would seem less confusing.
Smylers
Brad Oaks writes:
> On Mon, Mar 3, 2008 at 9:19 AM, Smylers <[EMAIL PROTECTED]> wrote:
>
> > demerphq writes:
> >
> > > It turned out the problem is that when the tests are root it seems to
> > > be not possible to create a directory that is not write
, but I don't know how you'd work out
which user to do it as.
Smylers
this thread) I'm intrigued
as to what's possible.
I use the debugger only infrequently, but perhaps with some tweaked
config I'd be inclined to use it more.
Any chance of a 'Me and My .perldb' (lightning) talk somewhere?
Smylers
work if you feel like claiming
this module will meet most testing needs, or be useful in most test
programs or something?
Smylers
f
> the TAP stream.
Wasn't there general agreement only a week or so ago to now allow plans
to be specified at the end rather than the start? I was presuming that
Schwern's suggestions were in the light of this other change.
Smylers
imposing, say, Unix-style
quoting on Windows users)?
The convention of using '--' to mean 'that's the end of my own
arguments' neatly avoids all of these issues.
Smylers
nd I
guessed what his words would say before I read them.
> In fact, it normally means "stop processing the following as switches
> and instead treat them as files".
Or possibly, it means "stop processing the following as switches".
Which is what it does mean in this case.
Smylers
as to learn whatever is chosen.
Also, because -- looks different from other options, it works well as a
divider, making it more obvious that _everything_ that follows is
distinct from that which went before, rather than it just being like a
'normal' option, where what follows are also options.
Smylers
> > > overkill to me.
>
> Agreed. I think the '--' is redundant
But is it doing harm? There are quite a few commands which use -- to
mean 'end of options; what follows is data' (where "data" can (and often
does mean) options to pass opaquely to another command being invoked).
Smylers
5.6 would be
> a good idea, I think.
Really? Personall I think it would be a _terrible_ idea for ISPs to
exclude such modules from their installations ...
(Oh, I see what you mean. Sorry!)
Smylers
e in environments where the purpose of
the sudoers restrictions is because you don't completely trust all of
your users.
Smylers
here.
The subject of this thread is Win32::GuiTest -- I know nothing about it,
but given it's a module for use with testing it seems on-topic for this
list.
Smylers
Eric Wilhelm writes:
> # from Smylers
> # on Thursday 16 August 2007 11:40 pm:
>
> > > I am certain that more than one 'extra tests' directory is needed,
> >
> > Why are you certain of this?
>
> Because I already have a use for three 'profiles
Ovid writes:
> --- Smylers <[EMAIL PROTECTED]> wrote:
>
> > > child directory I'm fairly certain of. I am certain that more
> > > than one 'extra tests' directory is needed,
> >
> > Why are you certain of this? It seems far from obvious
an unusual requirement.
> As for the 'xt' name:
Nobody is intuitively know what "xt" means, and it isn't obvious that
there's a need for the directory name to be short.
> I think anything starting with 't' would get annoying as far as
> tab-complete goes.
You'd only have to type 2 characters for the new directory name, and "t"
itself would obviously remain a single character that doesn't even
require pressing Tab.
Smylers
exist, so long
as you include the unique bug IDs somewhere in the description. You
just need to pass to the tracker the pattern that matches your format of
IDs from the descriptions; for the above example that'd be:
qr/\(bug \d+\)/
Smylers
simply removing the %INC entry if it's
found, so that it can be used safely in exactly this situation?
Would doing that silently obscure any genuine bugs?
Smylers
nd the like), which runtests is
also swallowing at the moment?
Smylers
st solution, and one which unblocks Test::Harness 3.0
> because TAP::Parser breaks compatibility in its current state, is to
> remove the syncing feature.
I have no view on whether syncing should be removed (or relegated to an
option, or whatever), but I am in favour of warnings showing up by
default.
Smylers
even
if not).
Then something reading that stream knows that if it supports the version
number in question it will be able to understand the stream, and that
otherwise it should give up.
Smylers
of
minimizing the number of people who have to cope with the change.
Smylers
Eric Wilhelm writes:
> # from Smylers
> # on Sunday 21 January 2007 11:50 pm:
>
> > Eric Wilhelm writes:
> >
> > > If that isn't enough, I suppose you could do "if the env var is an
> > > executable, run it and capture the output"?
> &
that
environment variable you can get them to run any code you want the next
time they install a Cpan module that doesn't explicitly set this
variable?
Smylers
7;re not inventing this but one actually made the code
> worse whith that kind of hack. IMHO, just enabling this kind of code
> is going against everything you want to achive, testable applications.
No, it's enabling you to test other code that is near an action which
absolutely cannot be run in a test environment, thereby making more of
the application testable.
Smylers
Michael G Schwern writes:
> A few people have asked how I do my CPAN scans. I keep a minicpan
> handy and have a little script called "grep_cpan" ...
>
> http://schwern.org/src/grep_cpan
404. But this works:
http://www.schwern.org/~schwern/src/grep_cpan
Smylers
the here-doc syntax has got very peculiar tastes!
Smylers
o modules like this
if only they'd just treat it as a string -- but instead overjealous
checking spots that it's a reference and declines to stringify it.
If you get a reference to a blessed object and that object has
overloaded stringification then please just treat it as a string, not a
reference.
Smylers
t; The idea of something working "better" than than the author expected
> is a bit dubious.
Sure -- it possibly happened by chance. Which is why the result usually
isn't interesting.
Smylers
are on Planet Perl then
probably quite a few folks are reading your output.
Smylers
rc that's on a different machine.
> That `%` expands to the filename for the active buffer. Very handy to
> know about.
Indeed:
:!cvs dif %
:lcd %:h
Smylers
David Landgren writes:
> Ovid wrote:
>
> > if ( $result->unexpectedly_succeeded ) { ... }
>
> todo_succeeded
That sounds good to me.
Smylers
e enough info.
>
> So, you got it wrong when I presume you were being careful. If that's
> not a clear demonstration that something could be a whole lot better
> then I don't know what is.
Note also that the :TestHelper attribute has been added to the sub, to
indicate that it's a sub that helps with testing.
See Aristotle's message earlier in the thread for the suggestion of
using that as a less verbose alternative than having to set the level
variable manually.
Smylers
Fergal Daly writes:
> On 12/07/06, Smylers <[EMAIL PROTECTED]> wrote:
>
> > I have this one-liner as ~/bin/pmv:
> >
> > #! /bin/sh
> > perl -m$1 -le 'print '$1'->VERSION || die "No VERSION in '$1'\n"'
>
>
e-liner as ~/bin/pmv:
#! /bin/sh
perl -m$1 -le 'print '$1'->VERSION || die "No VERSION in '$1'\n"'
> I think that calling ->VERSION is more correct.
So do I. In fact I used to use $VERSION in my script, but changed to
->VERSION after some situation in which it worked and $VERSION didn't.
Sorry, I can't right now remember what that was.
Smylers
demerphq writes:
> On 7/12/06, Smylers <[EMAIL PROTECTED]> wrote:
>
> > David Landgren writes:
> >
> > > Expected and actual has a long tradition in scientific endeavour,
>
> And are still sucky as they are different lengths meaning the two
> outputs
David Landgren writes:
> Expected and actual has a long tradition in scientific endeavour,
They strike me as the teams most intuitively recognizable and least open
to misinterpretation.
Smylers
t confusing trying to remember which are
TAP:: and which are TAPx:: modules.
Smylers
o to fix it. ...
How do you get authors to actually look at the CPANTS information and
make corrections? Well, we like competition. Make it a game!
So it was you -- or somebody impersonating you on this list -- who
managed to persuade me that actually Cpants being a game was a good
thing!
Smylers
rt of packages.
Basically you just need to do:
$ cpan2dist --format CPANPLUS::Dist::Deb Crypt::GeneratePassword
then wait for cpan-libcrypt-generatepassword-perl_0.03-1_all.deb to
spring into existence.
Smylers
in a particular way, then relying on that
output is not the same as relying on implementation details.
Smylers
the "the core is too big already" camp.
Um, surely File::Find and Memoize are already in the core?
Smylers
en you can use q to record a keyboard macro
for processing one line and moving on to the next, then it's just a case
of holding down the @ key to do as many lines as you want.
Smylers
pm'};
use_ok('Bar');
In general that seems a reasonable thing for use_ok to do itself: if you
want to test that the specified module can actually load right now then
you don't the results to be contaminated with what might've gone before.
Smylers
ould be as a deb package of
just the app, but with dependencies on any required modules (and with
debs of those modules if they aren't already available), but I realize
that not everybody is running an OS which uses debs so this isn't a
sufficient solution.
Smylers
lable, so we can presumably look to see what
the heuristic is ...
Smylers
n 1.15 was released as Scalar-List-Util-1.15.tar.gz, without the
"s".
This shouldn't matter: Perl dependencies are on modules, not on
distributions. And the names of the modules didn't change when the
package was named differently. If this is confusing ActiveState then
that sounds like a bug in their system.
Smylers
author v user distinction: any user can suddenly elect to
modify the code and become an author (even if only for modifying a
private version).
Smylers
If a bug is only in one place, it only needs fixing in one place ...
Smylers
terface properly -- but that's OK, so long as
existing uses are supported. The idea is that new code should be
written to use your interface, but existing code can be shoehorned into
working with it somehow.
> 6. I had done a lot of refactoring and revamp and broke a lot of the
> int
Michael G Schwern writes:
> I'm absorbing Test::Builder::Tester into the Test-Simple distribution.
Thank you for doing this -- a practical way of sorting out the
situation.
Smylers
--
May God bless us with enough foolishness to believe that we can make a
difference in this world, so
lly want to talk about it being an acronym, it should be:
"CPANTS" is an acronym for "CPAN Testing Service".
-- cos there you're talking about the words rather than about the
entities.
Smylers
--
May God bless us with enough foolishness to believe that we can make a
es/i. After the
> run, we'll see how many percent use it and try to find a regex that
> matches more dists.
As others have pointed out, ChangeLog is also popular and given special
treatment by Cpan Search; please allow CHANGES or ChangeLog.
Smylers
--
May God bless us with enough foolis
er didn't have Sub::Uplevel installed. I'm going to have to
> track down what's really causing that,
Sounds like a cunning plan by the Sub::Uplevel author to get you to add
that module as a prereq for all yours, thereby increasing his kwalitee.
Smylers
--
May God bless us with eno
Michael G Schwern writes:
> On Tue, Jul 12, 2005 at 07:45:35AM +0000, Smylers wrote:
>
> > A good way of putting assumptions into code is with (Michael's
> > excellent) Carp::Assert:
> >
> > assert $p || $q, 'Either $p or $q must be supplied' if DE
r mailing list, but I'd be happy to read about it here -- or
possibly on module-authors, which might be even more on-topic than this
list.
Smylers
--
May God bless us with enough foolishness to believe that we can make a
difference in this world, so that we can do what others claim cannot be done.
:
>
> bless {}, ref $class || $class;
>
> $class being false would be quite the error.
Ditto, so you could make the assumption explicit with an assertion. Or
perhaps something like Params::Validate would be better.
Smylers
--
May God bless us with enough foolishness to believe that we can make a
difference in this world, so that we can do what others claim cannot be done.
that fit on the first screenful don't give much clue that the
information would be provided if they did have any notes.)
But the scrolling is only necessary on distros containing large numbers
of modules, and PPI is quite unrepresentative in that respect!
Smylers
--
May God bless us with enough
t; > behaviour ...
>
> Yes. And I posit it should be the one that is most consistant.
That was my point -- that even if we agree to have a flag, it doesn't
help the debate at all, cos all of the original arguments still apply.
> And the existing logic is not consistant.
I reckon they're both consistent, just different.
Hmmm. I see we aren't even "consistent" on how to spell that particular
word! I can't be bothered to look it up to see which of us is right (or
whether both are valid) ...
Smylers
deep as the data structure goes, not
that there's a special rule for the top-level that's treated differently
from the others.
> is_deeply should be reliable and do what its name says.
I think everybody's in agreement about that! There's just the matter of
agreeing what i
which, presumably the only way to invoke the code-ref is without any
parameters, which might be completely inappropriate.
Smylers
--
May God bless us with enough foolishness to believe that we can make a
difference in this world, so that we can do what others claim cannot be done.
ncludes a literal tab character
anywhere in the distro's source!
Smylers
--
May God bless us with enough foolishness to believe that we can make a
difference in this world, so that we can do what others claim cannot be done.
to go to the effort of installing it if she
so desires.
(Note I'm not specifically agreeing with the point that shipping dev
tests makes sense -- I think it's fine for some authors to choose to do
so and some to choose not to; I'm merely disagreeing with the suggestion
that shippin
are the modules of poor quality but with high
kwalitee (and vice versa)? And what can be done to distinguish those
modules from modules of high (low) quality? It may be that removing the
pod coverage test criterion is an answer to that question (or it may
not).
> Why not give a kwalitee point f
th a lower ranking than others
through something that they can't change probably doesn't help here.
> We can/should debate the metrics, but not the philosophy of
> measurement.
It isn't the measurement that Andy was objecting to, but the
presentation of it as a per-user chart. As far as possible it should be
ensured that the measuring itself doesn't have negative consequences ...
Smylers
84 matches
Mail list logo
