this in a module:
succeed, rather than succeeded.
Cheers
Smylers
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
.html
Any thoughts?
Smylers
that
isn't in PMLIBDIRS?
Smylers
David Golden writes:
On Fri, May 15, 2009 at 12:11 PM, Smylers smyl...@stripey.com 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 being confusing
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
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
people's names.
Smylers
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
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 want to approach arguing
about the legal definition
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.
Yeah, that sounds good.
But only for users
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
start making use of the DB without asking
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'm just
, 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
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
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
by somebody else
for a different purpose, which could cause problems if your systems
later 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
Perl modules were installed as RPMs or Debian packages, not
by CPAN.pm from tarballs.
Smylers
privacy would seem less confusing.
Smylers
work out
which user to do it as.
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 writeable by root.
I think that can be reduced
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
were in the light of this other change.
Smylers
'that's the end of my own
arguments' neatly avoids all of these issues.
Smylers
.
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
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
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
restrictions is because you don't completely trust all of
your users.
Smylers
know nothing about it,
but given it's a module for use with testing it seems on-topic for this
list.
Smylers
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
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' in one project and I
can name a few others from elsewhere
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
at the moment?
Smylers
by the number a version with which it is
compatible (ideally the lowest such version, but it'll still work 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?
Nice -- so that if you manage to trick somebody into setting
to run any code you want the next
time they install a Cpan module that doesn't explicitly set this
variable?
Smylers
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
peculiar tastes!
Smylers
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
.
Smylers
Perl then
probably quite a few folks are reading your output.
Smylers
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
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
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 are offset on the screen making it harder to see
'-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
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'
These all fail for modules that do interesting things. For example
Test::NoWarnings performs a Test
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
::GeneratePassword
then wait for cpan-libcrypt-generatepassword-perl_0.03-1_all.deb to
spring into existence.
Smylers
on implementation details.
Smylers
.
Um, surely File::Find and Memoize are already in the core?
Smylers
the @ key to do as many lines as you want.
Smylers
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
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
what
the heuristic is ...
Smylers
version).
Smylers
place ...
Smylers
into
working with it somehow.
6. I had done a lot of refactoring and revamp and broke a lot of the
interface.
Sure; that's quite reasonable. But again, it doesn't preclude
compatibility now being added.
Best wishes
Smylers
--
May God bless us with enough foolishness to believe that we can make
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 that we can
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
difference in this world, so that we can
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 foolishness to believe that we can make a
difference in this world, so that we can do what others claim cannot
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 enough foolishness to believe that we can make a
difference
Michael G Schwern writes:
On Tue, Jul 12, 2005 at 07:45:35AM +, 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 DEBUG;
While I get where you're going, I don't see
, 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.
-- 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.
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 foolishness to believe that we can make a
difference in this world, so that we
to support both [behaviours]
off of the same code base.
Then we're still in the position of arguing which should be the default
behaviour ...
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.
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
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.
a kwalitee point for modules that bundle a test that
checks for kwalitee?
If it produces a good correlation, then yes, have such a criterion.
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 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 shipping a dev test _necessarily_ imposes a burden on mere users of
the module.)
Smylers
--
May God bless us with enough foolishness
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.
74 matches
Mail list logo
