Benchmark-Perl-Formance-Cargo
view release on metacpan or search on metacpan
share/P6STD/boot/STD.pmc view on Meta::CPAN
infix_postfix_meta_operator => [ qw/infix_postfix_meta_operator__S_206Equal__PEEK/ ],
infix_prefix_meta_operator => [ qw/infix_prefix_meta_operator__S_199Bang__PEEK infix_prefix_meta_operator__S_200R__PEEK infix_prefix_meta_operator__S_201S__PEEK infix_prefix_meta_operator__S_202X__PEEK infix_prefix_meta_operator__S_203Z__PEEK/ ],
initializer => [ qw/initializer__S_165Equal__PEEK initializer__S_166ColonEqual__PEEK initializer__S_167ColonColonEqual__PEEK initializer__S_168DotEqual__PEEK/ ],
module_name => [ qw/module_name__S_038normal__PEEK/ ],
multi_declarator => [ qw/multi_declarator__S_057multi__PEEK multi_declarator__S_058proto__PEEK multi_declarator__S_059only__PEEK multi_declarator__S_060null__PEEK/ ],
numeric => [ qw/numeric__S_136rational__PEEK numeric__S_137complex__PEEK numeric__S_138number__PEEK/ ],
package_declarator => [ qw/package_declarator__S_047class__PEEK package_declarator__S_048grammar__PEEK package_declarator__S_049module__PEEK package_declarator__S_050package__PEEK package_declarator__S_051role__PEEK package_declarator__S_052knowhow__...
postcircumfix => [ qw/postcircumfix__S_207Paren_Thesis__PEEK postcircumfix__S_208Bra_Ket__PEEK postcircumfix__S_209Cur_Ly__PEEK postcircumfix__S_210Lt_Gt__PEEK postcircumfix__S_211LtLt_GtGt__PEEK postcircumfix__S_212Fre_Nch__PEEK/ ],
postfix => [ qw/postfix__S_215i__PEEK postfix__S_217MinusGt__PEEK postfix__S_218PlusPlus__PEEK postfix__S_219MinusMinus__PEEK/ ],
postfix_prefix_meta_operator => [ qw/postfix_prefix_meta_operator__S_198Nch__PEEK/ ],
prefix => [ qw/prefix__S_220PlusPlus__PEEK prefix__S_221MinusMinus__PEEK prefix__S_223Bang__PEEK prefix__S_224Plus__PEEK prefix__S_225Minus__PEEK prefix__S_226TildeTilde__PEEK prefix__S_227Tilde__PEEK prefix__S_228QuestionQuestion__PEEK prefix__S_229...
prefix_postfix_meta_operator => [ qw/prefix_postfix_meta_operator__S_197Fre__PEEK/ ],
quote => [ qw/quote__S_139SlashSlash__PEEK quote__S_140Slash_Slash__PEEK quote__S_141qq__PEEK quote__S_142q__PEEK quote__S_143Q__PEEK quote__S_155rx__PEEK quote__S_156m__PEEK quote__S_157ms__PEEK quote__S_158s__PEEK quote__S_159ss__PEEK quote__S_160t...
quote_mod => [ qw/quote_mod__S_144w__PEEK quote_mod__S_145ww__PEEK quote_mod__S_146p__PEEK quote_mod__S_147x__PEEK quote_mod__S_148to__PEEK quote_mod__S_149s__PEEK quote_mod__S_150a__PEEK quote_mod__S_151h__PEEK quote_mod__S_152f__PEEK quote_mod__S_1...
regex_declarator => [ qw/regex_declarator__S_065regex__PEEK regex_declarator__S_066token__PEEK regex_declarator__S_067rule__PEEK/ ],
routine_declarator => [ qw/routine_declarator__S_061sub__PEEK routine_declarator__S_062method__PEEK routine_declarator__S_063submethod__PEEK routine_declarator__S_064macro__PEEK/ ],
scope_declarator => [ qw/scope_declarator__S_040my__PEEK scope_declarator__S_041our__PEEK scope_declarator__S_042anon__PEEK scope_declarator__S_043state__PEEK scope_declarator__S_044augment__PEEK scope_declarator__S_045supersede__PEEK scope_declarato...
special_variable => [ qw/special_variable__S_089Dollar_a2___PEEK special_variable__S_090DollarBang__PEEK special_variable__S_091DollarBangCur_Ly__PEEK special_variable__S_092DollarSlash__PEEK special_variable__S_093DollarTilde__PEEK special_variable_...
statement_control => [ qw/statement_control__S_000need__PEEK statement_control__S_001import__PEEK statement_control__S_002use__PEEK statement_control__S_003no__PEEK statement_control__S_004if__PEEK statement_control__S_005unless__PEEK statement_contr...
statement_mod_cond => [ qw/statement_mod_cond__S_031if__PEEK statement_mod_cond__S_032unless__PEEK statement_mod_cond__S_033when__PEEK/ ],
statement_mod_loop => [ qw/statement_mod_loop__S_034while__PEEK statement_mod_loop__S_035until__PEEK statement_mod_loop__S_036for__PEEK statement_mod_loop__S_037given__PEEK/ ],
share/P6STD/boot/STD.pmc view on Meta::CPAN
$C->_SUBSUMEr(['O'], sub {
my $C = shift;
$C->O(%loose_unary)
})
} else { () }
});
}
;
## token prefix:sym<not>
sub prefix__S_324not__PEEK { $_[0]->_AUTOLEXpeek('prefix__S_324not', $retree) }
sub prefix__S_324not {
no warnings 'recursion';
my $self = shift;
local $::CTX = $self->callm() if $::DEBUG & DEBUG::trace_call;
my $C = $self->cursor_xact("RULE prefix__S_324not");
my $xact = $C->xact;
my $S = $C->{'_pos'};
share/PerlCritic/Critic/Policy/NamingConventions/Capitalization.pm view on Meta::CPAN
# Got my or state: treat as local lexical variable
return $self->_check_capitalization(
symbol_without_sigil($name), $name, 'local_lexical_variable', $elem,
);
}
sub _label_capitalization {
my ($self, $elem, $name) = @_;
return if _is_not_real_label($elem);
( my $label = $elem->content() ) =~ s< \s* : \z ><>xms;
return $self->_check_capitalization($label, $label, 'label', $elem);
}
sub _check_capitalization {
my ($self, $to_match, $full_name, $name_type, $elem) = @_;
my $test = $self->{"_${name_type}_test"};
if ( my $message = $test->($to_match) ) {
return $self->violation(
share/PerlCritic/Critic/Policy/NamingConventions/Capitalization.pm view on Meta::CPAN
return if
$great_grand_parent and not $great_grand_parent->isa('PPI::Document');
# Make sure we aren't really in a continue block.
my $prior_to_grand_parent = $grand_parent->sprevious_sibling();
return $TRUE if not $prior_to_grand_parent;
return $TRUE if not $prior_to_grand_parent->isa('PPI::Token::Word');
return $prior_to_grand_parent->content() ne 'continue';
}
sub _is_not_real_label {
my $elem = shift;
# PPI misparses part of a ternary expression as a label
# when the token to the left of the ":" is a bareword.
# See http://rt.cpan.org/Ticket/Display.html?id=41170
# For example...
#
# $foo = $condition ? undef : 1;
#
# PPI thinks that "undef" is a label. To workaround this,
share/PerlCritic/Critic/Policy/RegularExpressions/ProhibitCaptureWithoutTest.pm view on Meta::CPAN
my $content = $xfer->content();
# Anything in the hash is always a transfer of control.
return $TRUE if $UNAMBIGUOUS_CONTROL_TRANSFER{ $content };
# A goto is not unambiguous on the face of it, but at least some forms of
# it can be accepted.
q<goto> eq $content
and return _unambiguous_goto( $xfer, $elem );
# Anything left at this point is _not_ an unambiguous transfer of control
# around whatever follows it.
return;
}
# Determine whether the given goto represents an unambiguous transfer of
# control around anything that follows it in the same block. The arguments are
# the element to check, and the capture variable that is the subject of this
# call to the policy.
sub _unambiguous_goto {
my ( $xfer, $elem ) = @_;
share/PerlCritic/Critic/Policy/ValuesAndExpressions/ProhibitEscapedCharacters.pm view on Meta::CPAN
sub default_severity { return $SEVERITY_LOW }
sub default_themes { return qw(core pbp cosmetic) }
sub applies_to { return qw(PPI::Token::Quote::Double
PPI::Token::Quote::Interpolate) }
#-----------------------------------------------------------------------------
sub violates {
my ( $self, $elem, undef ) = @_;
my $not_escaped = qr/(?<!\\)(?:\\\\)*/xms;
my $hex = qr/\\x[\dA-Fa-f]{2}/xms;
my $widehex = qr/\\x[{][\dA-Fa-f]+[}]/xms;
my $oct = qr/\\[01][0-7]/xms;
if ($elem->content =~ m/$not_escaped (?:$hex|$widehex|$oct)/xmso) {
return $self->violation( $DESC, $EXPL, $elem );
}
return; #ok!
}
1;
__END__
#-----------------------------------------------------------------------------
share/PerlCritic/Critic/Policy/ValuesAndExpressions/ProhibitLongChainsOfMethodCalls.pm view on Meta::CPAN
This policy has one option: C<max_chain_length> which controls how far
the code is allowed to navigate. The default value is 3.
=head1 TO DO
Add a C<class_method_exemptions> option to allow for things like
File::Find::Rule
->name('*.blah')
->not_name('thingy')
->readable()
->directory()
->in(@roots);
=head1 AUTHOR
Elliot Shank C<< <perl@galumph.com> >>
share/RegexpCommonTS/t/test_comments.t view on Meta::CPAN
[[qw /Pascal/, [Pascal => 'Workshop']] => "(*", "*)"],
[[qw /Pascal/] => "{", "*)"],
[[qw /Pascal/] => "(*", "}"],
);
foreach my $info (@ids) {
my ($mark, $languages) = @$info;
my $not_mark = $mark eq '#' ? '!' : '#';
foreach my $language (@$languages) {
if (ref $language) {
try $RE{comment}{$language -> [0]}{$language -> [1]};
$language = join ":" => @$language;
}
else {
try $RE{comment}{$language};
}
$M .= "# $language\n";
share/RegexpCommonTS/t/test_comments.t view on Meta::CPAN
pass qq !${mark}${mark}!;
pass qq !${mark}a comment${mark}!;
pass qq !${mark}/*a comment */${mark}!;
pass qq !${mark}/************${mark}!;
pass qq !${mark}/////////////${mark}!;
fail qq !${mark}a${mark}${mark}multiline${mark}${mark}comment${mark}!;
fail qq !${mark}a comment!;
fail qq !${mark}/*a comment */!;
fail qq !${mark}/************!;
fail qq !${mark}/////////////!;
fail qq !${not_mark}${mark}!;
fail qq !${not_mark}a comment${mark}!;
fail qq !${not_mark}/*a comment */${mark}!;
fail qq !${not_mark}/************${mark}!;
fail qq !${not_mark}${mark}////////////${mark}!;
fail qq !//a comment${mark}!;
fail qq !///*a comment */${mark}!;
fail qq !///************${mark}!;
fail qq !///////////////${mark}!;
fail qq !//a${mark}//multiline${mark}//comment${mark}!;
fail qq !//a comment!;
fail qq !///*a comment */!;
fail qq !///************!;
fail qq !///////////////!;
next if $language eq 'Pascal:Workshop';
share/SpamAssassin/easy_ham/00914.a24840d53c5f49a00e66fa4425e4626d view on Meta::CPAN
communication protocols.
I believe these are profound limitations, which we are already
encountering in practice. Spam, for example, is in the eye of the
beholder, yet our email protocols and tools do not acknowledge the
separate interests of senders and receivers. Slamming, for another,
unfairly advantages the bidder with the lowest-latency connection to a
centralized auction server. Sharing ad-hoc wireless networks is yet a
third example of decentralized resource allocation. Furthermore, as
abstract as centralization-induced failures might seem today, these
limits will _not_ improve as the cost of computing, storage, and
communication bandwidth continue to plummet. Instead, the speed of light
and human independence constitute _fundamental_ limits to centralized
information representation, and hence centralized software architecture.
share/SpamAssassin/easy_ham/01199.59f410d0b6c37510d6a29d0d02f62101 view on Meta::CPAN
<mailto:rpm-list-request@freshrpms.net?subject=subscribe>
List-Id: Freshrpms RPM discussion list <rpm-zzzlist.freshrpms.net>
List-Unsubscribe: <http://lists.freshrpms.net/mailman/listinfo/rpm-zzzlist>,
<mailto:rpm-list-request@freshrpms.net?subject=unsubscribe>
List-Archive: <http://lists.freshrpms.net/pipermail/rpm-zzzlist/>
X-Original-Date: Mon, 30 Sep 2002 21:42:04 +0200
Date: Mon, 30 Sep 2002 21:42:04 +0200
Hi.
Are there any reasons _not_ to use the new apt releases on RH 7.x?
--
reiserfsck ist bekannt dafür, daß es leere Dateisysteme zurückläßt.
Gut, formaljuristisch hat er das Dateisystem in einen wohldefinierten
Zustand versetzt, aber ... nunja. Man erwartet schon irgendwie, daß
noch ein paar Daten drauf sind danach. -- Felix v. Leitner, dasr
_______________________________________________
RPM-List mailing list <RPM-List@freshrpms.net>
http://lists.freshrpms.net/mailman/listinfo/rpm-list
share/SpamAssassin/easy_ham/01201.2da17f4409568ea3fad63130544ede70 view on Meta::CPAN
<mailto:rpm-list-request@freshrpms.net?subject=subscribe>
List-Id: Freshrpms RPM discussion list <rpm-zzzlist.freshrpms.net>
List-Unsubscribe: <http://lists.freshrpms.net/mailman/listinfo/rpm-zzzlist>,
<mailto:rpm-list-request@freshrpms.net?subject=unsubscribe>
List-Archive: <http://lists.freshrpms.net/pipermail/rpm-zzzlist/>
X-Original-Date: Mon, 30 Sep 2002 22:00:02 +0200
Date: Mon, 30 Sep 2002 22:00:02 +0200
Once upon a time, Ralf wrote :
> Are there any reasons _not_ to use the new apt releases on RH 7.x?
Hmmm... I don't see any :-)
My main concern is that when rebuilding the recent packages I've made for
Psyche on Valhalla, I'd need to lower the "Release:" tag (to keep an
upgrade working), and that would f*ck up my CVS repository which is on my
Valhalla box (well, I'm exagerating, It'll just make it more difficult for
me) ;-)
Sure, there are easy ways around this, but the easiest for me will be to
wait until I upgrade my main box to Psyche and have Valhalla only on a
share/SpamAssassin/easy_ham/02242.069e8b99ee8a2d62ec97d0e9d389aa5f view on Meta::CPAN
Received: from dogma.slashnull.org (localhost [127.0.0.1]) by
dogma.slashnull.org (8.11.6/8.11.6) with ESMTP id g9380XK19947 for
<jm@jmason.org>; Thu, 3 Oct 2002 09:00:33 +0100
Message-Id: <200210030800.g9380XK19947@dogma.slashnull.org>
To: yyyy@spamassassin.taint.org
From: diveintomark <rssfeeds@spamassassin.taint.org>
Subject: Cast not the first stone
Date: Thu, 03 Oct 2002 08:00:33 -0000
Content-Type: text/plain; encoding=utf-8
URL: http://diveintomark.org/archives/2002/10/02.html#cast_not_the_first_stone
Date: 2002-10-02T09:30:52-05:00
First Blood is Spilled at Record Industry Hearings[1]. “In a shocking
statement made by Back Street Boy, Kevin Richardson, he testified that they
have NEVER received a royalty check, and that they only took a large advance
after their third hit album in a row failed to earn them a penny in
royalties.”
share/SpamAssassin/easy_ham/02375.edeb9041e87f72ee99fa802021017fc2 view on Meta::CPAN
Received: from dogma.slashnull.org (localhost [127.0.0.1]) by
dogma.slashnull.org (8.11.6/8.11.6) with ESMTP id g9980FK25140 for
<jm@jmason.org>; Wed, 9 Oct 2002 09:00:15 +0100
Message-Id: <200210090800.g9980FK25140@dogma.slashnull.org>
To: yyyy@spamassassin.taint.org
From: diveintomark <rssfeeds@spamassassin.taint.org>
Subject: Barney Not Found
Date: Wed, 09 Oct 2002 08:00:15 -0000
Content-Type: text/plain; encoding=utf-8
URL: http://diveintomark.org/archives/2002/10/08.html#barney_not_found
Date: 2002-10-08T22:41:03-05:00
Microsoft Knowledge Base Article Q172668: Barney Fun on Imagination Island
Error Message: Barney Not Found[1]. Microsoft ActiMates Interactive Barney may
conflict with a wide range of radio-operated electronic devices, including
burglar alarms, resulting in the dreaded “Barney Not Found” error.
To resolve this problem, Microsoft recommends turning off your burglar alarm.
Incidentally, this is the funniest MS KBase article I've seen since Earth
Rotates in Wrong Direction[2].
share/SpamAssassin/easy_ham_2/00072.198398984661d0b6dc676ad30d6f2884 view on Meta::CPAN
|[ ... ]
| the issue here is tar(1) (and cpio(1)) archives always
| contain the data for each name of a hard link. [ ... ]
ARRGGGHHHH!!!!!
profuse apologies, the wrong version of my reply was posted
(blame it on being late for the pub). ;-(
the above is almost pure B*S* --- I got my `tar's and `cpio's
confused. what I said _is_ correct, but for cpio(1) archives;
tar(1) archives do _not_ replicate the data for hard links.
I spotted this confusion on my part before I posted my reply,
and re-wrote it to be more correct, yet somehow the wrong
version got sent anyways. ARRGGGHHHH!!!!! ;-( ;-( ;-(
anyways, GNU `cpio -p' does not do spurious reads or writes.
GNU `tar cf - ... | tar xf - ...' also does not, albeit each
`tar' both reads and writes the data. hence, there is twice
(not thrice!) the I/O of `cpio -p', maybe an issue for c.60Gb.
share/SpamAssassin/easy_ham_2/00196.8f7b9e0c0114f5fde680158804bc2f9a view on Meta::CPAN
build up your character as a series of composes of the root or
fundamental strokes ("radicals", I think they are called), and
then "commit" the composite character to the application.
( yes, keyboarding these scripts _is_ quite slow, I believe
a good typist can only do a few characters a minute!
and I assume using a qwerty keyboard is very painful. )
some XIMs compose "in place", others do it on a special line,
and some seem to do it in a special window (or the root?).
also, some(/most?) XIMs apparently support a US-ASCII input
mode as well --- _not_ a general Latin-alphabet input mode,
which seems to require another TLA, called KBD, and which
apparently doesn't work when an XIM is also being used? ---
implying you have to switch back and forth between US-ASCII
input mode (what us English-speakers would call "normal"
keyboarding/typing), and the other input (e.g., Chinese).
I'm not sure, but I have the impression the switch is often
a toggle, and something like <Control><CapsLock>.
many apologies if this is completely wrong or too misleading.
share/SpamAssassin/easy_ham_2/00200.a85d0ee8b147e0d0de9db7bc84117551 view on Meta::CPAN
I think the Microsoft Global IME has a 'stroke' mode where
you can build up a character stroke by stroke, but you'd only
use that when you know the character you want but you don't
know how to pronounce it.
>
> some XIMs compose "in place", others do it on a special line,
> and some seem to do it in a special window (or the root?).
> also, some(/most?) XIMs apparently support a US-ASCII input
> mode as well --- _not_ a general Latin-alphabet input mode,
> which seems to require another TLA, called KBD, and which
> apparently doesn't work when an XIM is also being used? ---
> implying you have to switch back and forth between US-ASCII
> input mode (what us English-speakers would call "normal"
> keyboarding/typing), and the other input (e.g., Chinese).
> I'm not sure, but I have the impression the switch is often
> a toggle, and something like <Control><CapsLock>.
Probably most often Ctrl-Space. That's what the Microsoft Global
Input Method Editor uses and what xcin uses IIRC.
share/SpamAssassin/easy_ham_2/00346.2f9b84c3f47ce85fcf3f7ef74b9e0ac6 view on Meta::CPAN
Precedence: bulk
List-Id: Irish Linux Users' Group <ilug.linux.ie>
X-Beenthere: ilug@linux.ie
Quoting Paul Linehan (plinehan@yahoo.com):
> What is the GPL all about then?
(1) I'm sure you are not _actually_ under the delusion that everything
on a typical Linux distribution issued subject to the terms of the GNU
GPL. For one thing, it seems difficult to imagine you _not_ being aware
that XFree86 is under the X/MIT licence, that Perl is under the Perl
Artistic Licence, that Apache is under the Apache licence, and that
numerous BSD utilities are under the BSD licence.
Furthermore, xv, Acrobat Reader, pine, pico, Netscape Communicator, and
a whole slew of other applications typically included aren't under any
open source licence at all, but rather are proprietary.
(2) You seem, in any event, to be under a misconception as to what the
GPL provides, as to code under its umbrella. It says (in part) that
_if_ you have lawfully received a copy of covered binary code, then you
may insist on one of certain forms of access to the matching source
code. Please note that it does _not_ guarantee you any rights
whatsoever if nobody's decided to give you a lawful copy.
> But *_surely_* they cannot BSD Linux? It's not theirs to BSD!
Again, you seem to be under a misconception. If you check, I'm quite
confident you'll see that SuSE are in full compliance with GPL v. 2's
source-code access provisions concerning GPLed code included in their
distribution. And no, nobody has the legal right to alter licence terms
to someone else's copyrighted property. But you have not cited any
reasons to believe that SuSE have done any of those things.
share/SpamAssassin/easy_ham_2/00347.345d2c25c6e5e7255b8f53291ff8ed9d view on Meta::CPAN
> "proprietary" license. There may be other third-party commercial
> products on there as well, which cannot be freely copied under the
> GPL.
Indeed.
The ftp'able tree (e.g., 8.0 for i386) contains to my knowledge only
items whose licences allow public redistribution, even where they aren't
open source. The retail boxed sets (Personal Edition, Professional
Edition, and Enterprise Edition) _add_ a number of additional
proprietary apps that are very much _not_ freely redistributable.
I made a list, a while back:
Freely redistributable proprietary apps in SuSE
----------------------------------------------
UofW pine/pico/pilot
John Bradley's xv graphics tool
T.C. Zhao and Mark Overmars's xforms/xformsd graphics toolkit
(some others)
NON-freely redistributable apps (in boxed sets):
share/SpamAssassin/easy_ham_2/00363.2c66a99268facef9c5dab8c1f7b81190 view on Meta::CPAN
> All I want is the OS and GNU apps. I was under the impression that for
> *_those_* all one needed was to pay for the media and not for the code
> itself?
>
> Ai-je tort?
Mais si.
You are indeed under a misconception, and may want to read the text of
the GPL to verify this fact. The GPL does _not_ entitle you to a copy
of any binary software. Section 2 provides for rights to access to
matching source code _if_ you have lawfully received a copy of a covered
binary. That section provides three alternative mechanisms for the
distributor to provide such access. And SuSE _do_ actually provide
exactly that access.
Or so I think to be the case. If you believe there's some GPLed
codebase that you can lawfully receive from SuSE whose matching source
code they are not making available exactly as required, please tell us
which codebase that is. (That would be SuSE Linux AG's headache, not
share/SpamAssassin/easy_ham_2/00363.2c66a99268facef9c5dab8c1f7b81190 view on Meta::CPAN
will "taint" their copyrights and force them to put their property under
the GPL. It's simply not so.
> If I wanted support from SuSE, that would be a different issue, and
> one for which I would be willing to pay.
That's nice, but they're not _offering_ the exact contents of the boxed
sets free of charge and lawful to duplicate & redistribute, or "borrow".
For one thing, as you will have noticed from my earlier listing of
components, the boxed sets' CD-ROMs include quite a lot of _third-party_
proprietary software. SuSE Linux AG _cannot_ allow you (or your friend)
to hand out copies of that software freely, because it's not theirs in
the first place.
> I have a friend with 7.3 - I think that I'll end up doing that!
If you mean the 3-CD core set of RH 7.3, good. It's a quite decent
distribution. But bear in mind that the RH 7.3 boxed sets include
some other third-party applications whose owners would be very upset to
find them being copied or "borrowed".
> I have now realised this, thanks to your kind explanations. I can
> borrow them, but not copy them?
No.
Look, it's a collection of software, many elements of which may not be
lawfully just given out to multiple people: Your friend installing it,
then _not_ erasing it but merely letting you "borrow" the CDs results in
the product being installed in multiple places. That's unauthorised
copying.
> And, as I've tried to explain, is not the licence terms on, say,
> trials for commercial company x to which I object, it is the way SuSE
> appears, at least to my I.T. peasant self, to have mixed up
> proprietary and open stuff.
Well, if you don't like SuSE, then you probably won't like Caldera
eDesk, Xandros Desktop, Lycoris Deskop LX, Libranet, Lindows, or KRUD,
share/SpamAssassin/easy_ham_2/00438.a4e08ec27cc4d6d5dd27d43178d3bc17 view on Meta::CPAN
off from Philips Electronics in 1998) invented and rather tightly
control the format, though other companies such as Verbatim do make
compatible media under licence.
If you're reasonably serious about backup, you need to plan for a
rotational backup scheme and retirement of tapes as they become worn
(and well before they start failing). That requires at least a couple
of dozen tapes for the first couple of years. Therefore, cost and
availability of media are (or should be) a major factor. Also, tape
heads wear out and need to be replaced (more rapidly for helical-scan
systems -- which ADR turns out _not_ to be), and somehow that always
ends up being cheaper for tape technologies in which there is heavy
competition.
The less-tangible consideration that comes most immediately to mind is
that, if one's OnStream ADR drive fails, the only possible replacement
that would suffice to restore your accumulated backup sets is another
OnStream ADR drive. In that sense, you're somewhat locked in: I'm
not seeing ADR drives from anyone else (though I might have missed
them).
share/SpamAssassin/easy_ham_2/00997.878a2f3b9a8d62c876f7d17819271678 view on Meta::CPAN
List-Post: <mailto:fork@spamassassin.taint.org>
List-Subscribe: <http://xent.com/mailman/listinfo/fork>, <mailto:fork-request@xent.com?subject=subscribe>
List-Id: Friends of Rohit Khare <fork.xent.com>
List-Unsubscribe: <http://xent.com/mailman/listinfo/fork>,
<mailto:fork-request@xent.com?subject=unsubscribe>
List-Archive: <http://xent.com/pipermail/fork/>
Date: Sun, 11 Aug 2002 06:32:35 +0000
Gary Lawrence Murphy:
>This is for the whitelist fans: Can someone please tell us why the
>following extremely frequent spam header pattern would _not_ pass a
>whitelist test? The letter itself is most certainly spam/viral and
>was most certainly not sent by me, but I see no way you might tell that it
>was not, nor can I see how I might charge the sender with fraud for having
>'impersonated' my account. .. My uneducated guess is that all they need to
>jump expensive whitelist
>walls would be buckshot a spam-laden Klez ..
There are several issues here.
(1) For reasons that have nothing to do with
share/SpamAssassin/easy_ham_2/00998.f58f417a784b56b196823b5052a45eb1 view on Meta::CPAN
List-Post: <mailto:fork@spamassassin.taint.org>
List-Subscribe: <http://xent.com/mailman/listinfo/fork>, <mailto:fork-request@xent.com?subject=subscribe>
List-Id: Friends of Rohit Khare <fork.xent.com>
List-Unsubscribe: <http://xent.com/mailman/listinfo/fork>,
<mailto:fork-request@xent.com?subject=unsubscribe>
List-Archive: <http://xent.com/pipermail/fork/>
Date: Sun, 11 Aug 2002 00:57:43 -0700
Gary Lawrence Murphy writes:
> This is for the whitelist fans: Can someone please tell us why the
> following extremely frequent spam header pattern would _not_ pass a
> whitelist test? The letter itself is most certainly spam/viral and
> was most certainly not sent by me, but I see no way you might tell
> that it was not, nor can I see how I might charge the sender with
> fraud for having 'impersonated' my account.
If you crypto-sign your outgoing mail, you don't have to set
your mailwall whitelist to accept unsigned mail spoofed as being
from you.
Similarly, if you include some weaker token or checksum that
share/SpamAssassin/easy_ham_2/01235.3a679e506c7f862dda03736804009e92 view on Meta::CPAN
> Skipping all RPM build parts except for the actual packing is not
> possible
Actually it is (sort of).
To answer partly the original question, this might have been useful once
the %files error was corrected :
rpmbuild -bi --short-circuit <specfile>
This will skip all the way to the %install and start from there. Of course,
you need to have already done everything else before, and this will _not_
produce any rpm files, but will at least tell you if everything is now able
to finish successfully.
Sure, it's not perfect since if the %files error was actually because
entries were missing you'll notice it only once the package is really
installed. But for multiple typos in the %files section (like when you're
writing a spec file after 2AM ;-)) it can come in handy :-)
It's also very useful if you need to override some Makefile variables
during install, when the simple cases like "%makeinstall" or "make install
share/SpamAssassin/easy_ham_2/01283.6e24c23f56e6a4bfd0f06e9884dfbe0c view on Meta::CPAN
subject_tag **SPAM**
wash ('tty') ~ 337 -> exim -bt engingwarez@runjiri.co.ke
eng.ngware@runji.co.ke
deliver to enginngware in domain runjiri.co.ke
director = spamcheck_director, transport = spamcheck
However when I check the mail delivered to this mailbox, SA has _not_ added any headers
to it.
PERTINENT: I also run a Virus Scanner called DRWEB via Exim's system filter and the rules
that I have applied are:
if not first_delivery or
$received_protocol is "drweb-scanned" or
$received_protocol is "spam-scanned"
then
finish
share/SpamAssassin/easy_ham_2/01312.715fe5f6f31d47697d5a8f625fd2e49f view on Meta::CPAN
Date: Wed, 24 Jul 2002 06:52:19 +0200
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by dogma.slashnull.org
id g6O4wo421169
From: Matt Kettler <mkettler@evi-inc.com>
> Hmm, I think that Marc, being one of the most active and prolific posters
> to this list, certainly understands SA much better than most. Certainly
Frequency of messages does _not_ let you draw valid conclusions about the
understanding of the issues at hand of the sender.
IMHO it's sometimes even inversely proportional.
> Marc is an active and prolific contributor to SA (gee, look, his name's
> even in the credit's page on the website!).
This should not impress you so much. At one time I even detected my name
on that page and I contributed less than a handful of rather simple rules.
That's not to say I don't appreciate Marc's contributions to the effort.
( run in 3.419 seconds using v1.01-cache-2.11-cpan-4d4bc49f3ae )