????

Your IP : 3.145.58.141


Current Path : /bin/
Upload File :
Current File : //bin/perlthanks

#!/usr/bin/perl
    eval 'exec /usr/bin/perl -S $0 ${1+"$@"}'
	if $running_under_some_shell;

my $config_tag1 = '5.16.3 - Thu Oct  1 16:52:28 UTC 2020';

my $patchlevel_date = 1601571147;
my $patch_tags = '+Fedora +Fedora +Fedora +Fedora +Fedora +Fedora +Fedora +Fedora +Fedora +Fedora +Fedora +Fedora +Fedora +Fedora +Fedora +Fedora +Fedora +Fedora +Fedora +Fedora +Fedora +Fedora +Fedora +Fedora +Fedora +RHEL +RHEL +RHEL +RHEL +RHEL +RHEL +RHEL +RHEL +RHEL +RHEL +RHEL +RHEL +RHEL +RHEL +RHEL +RHEL ';
my @patches = (
    'Fedora Patch1: Removes date check, Fedora/RHEL specific',
    'Fedora Patch3: support for libdir64',
    'Fedora Patch4: use libresolv instead of libbind',
    'Fedora Patch5: USE_MM_LD_RUN_PATH',
    'Fedora Patch6: Skip hostname tests, due to builders not being network capable',
    'Fedora Patch7: Dont run one io test due to random builder failures',
    'Fedora Patch9: Fix find2perl to translate ? glob properly (RT#113054)',
    'Fedora Patch10: Fix broken atof (RT#109318)',
    'Fedora Patch13: Clear $@ before \\"do\\" I/O error (RT#113730)',
    'Fedora Patch14: Do not truncate syscall() return value to 32 bits (RT#113980)',
    'Fedora Patch15: Override the Pod::Simple::parse_file (CPANRT#77530)',
    'Fedora Patch16: Do not leak with attribute on my variable (RT#114764)',
    'Fedora Patch17: Allow operator after numeric keyword argument (RT#105924)',
    'Fedora Patch18: Extend stack in File::Glob::glob, (RT#114984)',
    'Fedora Patch19: Do not crash when vivifying $|',
    'Fedora Patch20: Fix misparsing of maketext strings (CVE-2012-6329)',
    'Fedora Patch21: Add NAME headings to CPAN modules (CPANRT#73396)',
    'Fedora Patch22: Fix leaking tied hashes (RT#107000) [1]',
    'Fedora Patch23: Fix leaking tied hashes (RT#107000) [2]',
    'Fedora Patch24: Fix leaking tied hashes (RT#107000) [3]',
    'Fedora Patch25: Fix dead lock in PerlIO after fork from thread (RT#106212)',
    'Fedora Patch26: Make regexp safe in a signal handler (RT#114878)',
    'Fedora Patch27: Update h2ph(1) documentation (RT#117647)',
    'Fedora Patch28: Update pod2html(1) documentation (RT#117623)',
    'Fedora Patch29: Document Math::BigInt::CalcEmu requires Math::BigInt (CPAN RT#85015)',
    'RHEL Patch30: Use stronger algorithm needed for FIPS in t/op/crypt.t (RT#121591)',
    'RHEL Patch31: Make *DBM_File desctructors thread-safe (RT#61912)',
    'RHEL Patch32: Use stronger algorithm needed for FIPS in t/op/taint.t (RT#123338)',
    'RHEL Patch33: Remove CPU-speed-sensitive test in Benchmark test',
    'RHEL Patch34: Make File::Glob work with threads again',
    'RHEL Patch35: Fix CRLF conversion in ASCII FTP upload (CPAN RT#41642)',
    'RHEL Patch36: Do not leak the temp utf8 copy of namepv (CPAN RT#123786)',
    'RHEL Patch37: Fix duplicating PerlIO::encoding when spawning threads (RT#31923)',
    'RHEL Patch38: Add SSL support to Net::SMTP (CPAN RT#93823) [1]',
    'RHEL Patch39: Add SSL support to Net::SMTP (CPAN RT#93823) [2]',
    'RHEL Patch40: Add SSL support to Net::SMTP (CPAN RT#93823) [3]',
    'RHEL Patch41: Add SSL support to Net::SMTP (CPAN RT#93823) [4]',
    'RHEL Patch42: Do not overload \\"..\\" in Math::BigInt (CPAN RT#80182)',
    'RHEL Patch43: Fix CVE-2018-18311 Integer overflow leading to buffer overflow',
    'RHEL Patch44: Fix a spurious timeout in Net::FTP::close (CPAN RT#18504)',
    'RHEL Patch45: Fix day of year parsing (CPAN RT#88211)'
);

use warnings;
use strict;
use Config;
use File::Spec;		# keep perlbug Perl 5.005 compatible
use Getopt::Std;
use File::Basename 'basename';

sub paraprint;

BEGIN {
    eval { require Mail::Send;};
    $::HaveSend = ($@ eq "");
    eval { require Mail::Util; } ;
    $::HaveUtil = ($@ eq "");
    # use secure tempfiles wherever possible
    eval { require File::Temp; };
    $::HaveTemp = ($@ eq "");
    eval { require Module::CoreList; };
    $::HaveCoreList = ($@ eq "");
};

my $Version = "1.39";

#TODO:
#       make sure failure (transmission-wise) of Mail::Send is accounted for.
#       (This may work now. Unsure of the original author's issue -JESSE 2008-06-08)
#       - Test -b option

my( $file, $usefile, $cc, $address, $bugaddress, $testaddress, $thanksaddress,
    $filename, $messageid, $domain, $subject, $from, $verbose, $ed, $outfile,
    $fh, $me, $body, $andcc, %REP, $ok, $thanks, $progname,
    $Is_MSWin32, $Is_Linux, $Is_VMS, $Is_OpenBSD,
    $report_about_module, $category, $severity,
    %opt,
);

my $perl_version = $^V ? sprintf("%vd", $^V) : $];

my $config_tag2 = "$perl_version - $Config{cf_time}";

Init();

if ($opt{h}) { Help(); exit; }
if ($opt{d}) { Dump(*STDOUT); exit; }
if (!-t STDIN && !($ok and not $opt{n})) {
    paraprint <<"EOF";
Please use $progname interactively. If you want to
include a file, you can use the -f switch.
EOF
    die "\n";
}

Query();
Edit() unless $usefile || ($ok and not $opt{n});
NowWhat();
if ($outfile) {
    save_message_to_disk($outfile);
} else {
    Send();
    if ($thanks) {
	print "\nThank you for taking the time to send a thank-you message!\n\n";
    } else {
	print "\nThank you for taking the time to file a bug report!\n\n";
    }
}

exit;

sub ask_for_alternatives { # (category|severity)
    my $name = shift;
    my %alts = (
	'category' => {
	    'default' => 'core',
	    'ok'      => 'install',
	    # Inevitably some of these will end up in RT whatever we do:
	    'thanks'  => 'thanks',
	    'opts'    => [qw(core docs install library utilities)], # patch, notabug
	},
	'severity' => {
	    'default' => 'low',
	    'ok'      => 'none',
	    'thanks'  => 'none',
	    'opts'    => [qw(critical high medium low wishlist none)], # zero
	},
    );
    die "Invalid alternative ($name) requested\n" unless grep(/^$name$/, keys %alts);
    my $alt = "";
    my $what = $ok || $thanks;
    if ($what) {
	$alt = $alts{$name}{$what};
    } else {
 	my @alts = @{$alts{$name}{'opts'}};
    print "\n\n";
	paraprint <<EOF;
Please pick a $name from the following list:

    @alts
EOF
	my $err = 0;
	do {
	    if ($err++ > 5) {
		die "Invalid $name: aborting.\n";
	    }
        $alt = _prompt('', "\u$name", $alts{$name}{'default'});
		$alt ||= $alts{$name}{'default'};
	} while !((($alt) = grep(/^$alt/i, @alts)));
    }
    lc $alt;
}

sub Init {
    # -------- Setup --------

    $Is_MSWin32 = $^O eq 'MSWin32';
    $Is_VMS = $^O eq 'VMS';
    $Is_Linux = lc($^O) eq 'linux';
    $Is_OpenBSD = lc($^O) eq 'openbsd';

    if (!getopts("Adhva:s:b:f:F:r:e:SCc:to:n:T", \%opt)) { Help(); exit; };

    # This comment is needed to notify metaconfig that we are
    # using the $perladmin, $cf_by, and $cf_time definitions.

    # -------- Configuration ---------

    # perlbug address
    $bugaddress = 'perlbug@perl.org';

    # Test address
    $testaddress = 'perlbug-test@perl.org';

    # Thanks address
    $thanksaddress = 'perl-thanks@perl.org';

    if (basename ($0) =~ /^perlthanks/i) {
	# invoked as perlthanks
	$opt{T} = 1;
	$opt{C} = 1; # don't send a copy to the local admin
    }

    if ($opt{T}) {
	$thanks = 'thanks';
    }
    
    $progname = $thanks ? 'perlthanks' : 'perlbug';
    # Target address
    $address = $opt{a} || ($opt{t} ? $testaddress
			    : $thanks ? $thanksaddress : $bugaddress);

    # Users address, used in message and in From and Reply-To headers
    $from = $opt{r} || "";

    # Include verbose configuration information
    $verbose = $opt{v} || 0;

    # Subject of bug-report message
    $subject = $opt{s} || "";

    # Send a file
    $usefile = ($opt{f} || 0);

    # File to send as report
    $file = $opt{f} || "";

    # File to output to
    $outfile = $opt{F} || "";

    # Body of report
    $body = $opt{b} || "";
	
    # Editor
    $ed = $opt{e} || $ENV{VISUAL} || $ENV{EDITOR} || $ENV{EDIT}
	|| ($Is_VMS && "edit/tpu")
	|| ($Is_MSWin32 && "notepad")
	|| "vi";

    # Not OK - provide build failure template by finessing OK report
    if ($opt{n}) {
	if (substr($opt{n}, 0, 2) eq 'ok' )	{
	    $opt{o} = substr($opt{n}, 1);
	} else {
	    Help();
	    exit();
	}
    }

    # OK - send "OK" report for build on this system
    $ok = '';
    if ($opt{o}) {
	if ($opt{o} eq 'k' or $opt{o} eq 'kay') {
	    # force these options
	    unless ($opt{n}) {
		$opt{S} = 1; # don't prompt for send
		$opt{b} = 1; # we have a body
		$body = "Perl reported to build OK on this system.\n";
	    }
	    $opt{C} = 1; # don't send a copy to the local admin
	    $opt{s} = 1; # we have a subject line
	    $subject = ($opt{n} ? 'Not ' : '')
		    . "OK: perl $perl_version ${patch_tags}on"
		    ." $::Config{'archname'} $::Config{'osvers'} $subject";
	    $ok = 'ok';
	} else {
	    Help();
	    exit();
	}
    }

    # Possible administrator addresses, in order of confidence
    # (Note that cf_email is not mentioned to metaconfig, since
    # we don't really want it. We'll just take it if we have to.)
    #
    # This has to be after the $ok stuff above because of the way
    # that $opt{C} is forced.
    $cc = $opt{C} ? "" : (
	$opt{c} || $::Config{'perladmin'}
	|| $::Config{'cf_email'} || $::Config{'cf_by'}
    );

    if ($::HaveUtil) {
		$domain = Mail::Util::maildomain();
    } elsif ($Is_MSWin32) {
		$domain = $ENV{'USERDOMAIN'};
    } else {
		require Sys::Hostname;
		$domain = Sys::Hostname::hostname();
    }

    # Message-Id - rjsf
    $messageid = "<$::Config{'version'}_${$}_".time."\@$domain>"; 

    # My username
    $me = $Is_MSWin32 ? $ENV{'USERNAME'}
	    : $^O eq 'os2' ? $ENV{'USER'} || $ENV{'LOGNAME'}
	    : eval { getpwuid($<) };	# May be missing

    $from = $::Config{'cf_email'}
       if !$from && $::Config{'cf_email'} && $::Config{'cf_by'} && $me &&
               ($me eq $::Config{'cf_by'});
} # sub Init

sub Query {
    # Explain what perlbug is
    unless ($ok) {
	if ($thanks) {
	    paraprint <<'EOF';
This program provides an easy way to send a thank-you message back to the
authors and maintainers of perl.

If you wish to submit a bug report, please run it without the -T flag
(or run the program perlbug rather than perlthanks)
EOF
	} else {
	    paraprint <<"EOF";
This program provides an easy way to create a message reporting a
bug in the core perl distribution (along with tests or patches)
to the volunteers who maintain perl at $address.  To send a thank-you
note to $thanksaddress instead of a bug report, please run 'perlthanks'.

Please do not use $0 to send test messages, test whether perl
works, or to report bugs in perl modules from CPAN.

For help using perl, try posting to the Usenet newsgroup 
comp.lang.perl.misc.
EOF
	}
    }

    # Prompt for subject of message, if needed
    
    if ($subject && TrivialSubject($subject)) {
	$subject = '';
    }

    unless ($subject) {
	    print 
"First of all, please provide a subject for the message.\n";
	if ( not $thanks)  {
	    paraprint <<EOF;
This should be a concise description of your bug or problem
which will help the volunteers working to improve perl to categorize
and resolve the issue.  Be as specific and descriptive as
you can. A subject like "perl bug" or "perl problem" will make it
much less likely that your issue gets the attention it deserves.
EOF
	}

	my $err = 0;
	do {
        $subject = _prompt('','Subject');
	    if ($err++ == 5) {
		if ($thanks) {
		    $subject = 'Thanks for Perl';
		} else {
		    die "Aborting.\n";
		}
	    }
	} while (TrivialSubject($subject));
    }

    # Prompt for return address, if needed
    unless ($opt{r}) {
	# Try and guess return address
	my $guess;

	$guess = $ENV{'REPLY-TO'} || $ENV{'REPLYTO'} || $ENV{'EMAIL'}
	    || $from || '';

	unless ($guess) {
		# move $domain to where we can use it elsewhere	
        if ($domain) {
		if ($Is_VMS && !$::Config{'d_socket'}) {
		    $guess = "$domain\:\:$me";
		} else {
		    $guess = "$me\@$domain" if $domain;
		}
	    }
	}

	if ($guess) {
	    unless ($ok) {
		paraprint <<EOF;
Perl's developers may need your email address to contact you for
further information about your issue or to inform you when it is
resolved.  If the default shown is not your email address, please
correct it.
EOF
	    }
	} else {
	    paraprint <<EOF;
Please enter your full internet email address so that Perl's
developers can contact you with questions about your issue or to
inform you that it has been resolved.
EOF
	}

	if ($ok && $guess) {
	    # use it
	    $from = $guess;
	} else {
	    # verify it
        $from = _prompt('','Your address',$guess);
	    $from = $guess if $from eq '';
	}
    }

    if ($from eq $cc or $me eq $cc) {
	# Try not to copy ourselves
	$cc = "yourself";
    }

    # Prompt for administrator address, unless an override was given
    if( !$opt{C} and !$opt{c} ) {
	my $description =  <<EOF;
$0 can send a copy of this report to your local perl
administrator.  If the address below is wrong, please correct it,
or enter 'none' or 'yourself' to not send a copy.
EOF
	my $entry = _prompt($description, "Local perl administrator", $cc);

	if ($entry ne "") {
	    $cc = $entry;
	    $cc = '' if $me eq $cc;
	}
    }

    $cc = '' if $cc =~ /^(none|yourself|me|myself|ourselves)$/i;
    if ($cc) { 
        $andcc = " and $cc" 
    } else {
        $andcc = ''
    }

    # Prompt for editor, if no override is given
editor:
    unless ($opt{e} || $opt{f} || $opt{b}) {

    my $description;

	chomp (my $common_end = <<"EOF");
You will probably want to use a text editor to enter the body of
your report. If "$ed" is the editor you want to use, then just press
Enter, otherwise type in the name of the editor you would like to
use.

If you have already composed the body of your report, you may enter
"file", and $0 will prompt you to enter the name of the file
containing your report.
EOF

	if ($thanks) {
	    $description = <<"EOF";
It's now time to compose your thank-you message.

Some information about your local perl configuration will automatically
be included at the end of your message, because we're curious about
the different ways that people build and use perl. If you'd rather
not share this information, you're welcome to delete it.

$common_end
EOF
	} else {
	    $description =  <<"EOF";
It's now time to compose your bug report. Try to make the report
concise but descriptive. Please include any detail which you think
might be relevant or might help the volunteers working to improve
perl. If you are reporting something that does not work as you think
it should, please try to include examples of the actual result and of
what you expected.

Some information about your local perl configuration will automatically
be included at the end of your report. If you are using an unusual
version of perl, it would be useful if you could confirm that you
can replicate the problem on a standard build of perl as well.

$common_end
EOF
	}

    my $entry = _prompt($description, "Editor", $ed);
	$usefile = 0;
	if ($entry eq "file") {
	    $usefile = 1;
	} elsif ($entry ne "") {
	    $ed = $entry;
	}
    }
    if ($::HaveCoreList && !$ok && !$thanks) {
	my $description =  <<EOF;
If your bug is about a Perl module rather than a core language
feature, please enter its name here. If it's not, just hit Enter
to skip this question.
EOF

    my $entry = '';
	while ($entry eq '') {
        $entry = _prompt($description, 'Module');
	    my $first_release = Module::CoreList->first_release($entry);
	    if ($entry and not $first_release) {
		paraprint <<EOF;
$entry is not a "core" Perl module. Please check that you entered
its name correctly. If it is correct, quit this program, try searching
for $entry on http://rt.cpan.org, and report your issue there.
EOF

            $entry = '';
	} elsif (my $bug_tracker = $Module::CoreList::bug_tracker{$entry}) {
		paraprint <<"EOF";
$entry included with core Perl is copied directly from the CPAN distribution.
Please report bugs in $entry directly to its maintainers using $bug_tracker
EOF
            $entry = '';
        } elsif ($entry) {
	        $category ||= 'library';
	        $report_about_module = $entry;
            last;
        } else {
            last;
        }
	}
    }

    # Prompt for category of bug
    $category ||= ask_for_alternatives('category');

    # Prompt for severity of bug
    $severity ||= ask_for_alternatives('severity');

    # Generate scratch file to edit report in
    $filename = filename();

    # Prompt for file to read report from, if needed
    if ($usefile and !$file) {
filename:
	my $description = <<EOF;
What is the name of the file that contains your report?
EOF
	my $entry = _prompt($description, "Filename");

	if ($entry eq "") {
	    paraprint <<EOF;
It seems you didn't enter a filename. Please choose to use a text
editor or enter a filename.
EOF
	    goto editor;
	}

	unless (-f $entry and -r $entry) {
	    paraprint <<EOF;
'$entry' doesn't seem to be a readable file.  You may have mistyped
its name or may not have permission to read it.

If you don't want to use a file as the content of your report, just
hit Enter and you'll be able to select a text editor instead.
EOF
	    goto filename;
	}
	$file = $entry;
    }

    # Generate report
    open(REP,">$filename") or die "Unable to create report file '$filename': $!\n";
    my $reptype = !$ok ? ($thanks ? 'thank-you' : 'bug')
	: $opt{n} ? "build failure" : "success";

    print REP <<EOF;
This is a $reptype report for perl from $from,
generated with the help of perlbug $Version running under perl $perl_version.

EOF

    if ($body) {
	print REP $body;
    } elsif ($usefile) {
	open(F, "<$file")
		or die "Unable to read report file from '$file': $!\n";
	while (<F>) {
	    print REP $_
	}
	close(F) or die "Error closing '$file': $!";
    } else {
	if ($thanks) {
	    print REP <<'EOF';

-----------------------------------------------------------------
[Please enter your thank-you message here]



[You're welcome to delete anything below this line]
-----------------------------------------------------------------
EOF
	} else {
	    print REP <<'EOF';

-----------------------------------------------------------------
[Please describe your issue here]



[Please do not change anything below this line]
-----------------------------------------------------------------
EOF
	}
    }
    Dump(*REP);
    close(REP) or die "Error closing report file: $!";

    # Set up an initial report fingerprint so we can compare it later
    _fingerprint_lines_in_report();

} # sub Query

sub Dump {
    local(*OUT) = @_;

    # these won't have been set if run with -d
    $category ||= 'core';
    $severity ||= 'low';

    print OUT <<EFF;
---
Flags:
    category=$category
    severity=$severity
EFF

    if ($report_about_module ) { 
        print OUT <<EFF;
    module=$report_about_module
EFF
    }
    if ($opt{A}) {
	print OUT <<EFF;
    ack=no
EFF
    }
    print OUT <<EFF;
---
EFF
    print OUT "This perlbug was built using Perl $config_tag1\n",
	    "It is being executed now by  Perl $config_tag2.\n\n"
	if $config_tag2 ne $config_tag1;

    print OUT <<EOF;
Site configuration information for perl $perl_version:

EOF
    if ($::Config{cf_by} and $::Config{cf_time}) {
	print OUT "Configured by $::Config{cf_by} at $::Config{cf_time}.\n\n";
    }
    print OUT Config::myconfig;

    if (@patches) {
	print OUT join "\n    ", "Locally applied patches:", @patches;
	print OUT "\n";
    };

    print OUT <<EOF;

---
\@INC for perl $perl_version:
EOF
    for my $i (@INC) {
	print OUT "    $i\n";
    }

    print OUT <<EOF;

---
Environment for perl $perl_version:
EOF
    my @env =
        qw(PATH LD_LIBRARY_PATH LANG PERL_BADLANG SHELL HOME LOGDIR LANGUAGE);
    push @env, $Config{ldlibpthname} if $Config{ldlibpthname} ne '';
    push @env, grep /^(?:PERL|LC_|LANG|CYGWIN)/, keys %ENV;
    my %env;
    @env{@env} = @env;
    for my $env (sort keys %env) {
	print OUT "    $env",
		exists $ENV{$env} ? "=$ENV{$env}" : ' (unset)',
		"\n";
    }
    if ($verbose) {
	print OUT "\nComplete configuration data for perl $perl_version:\n\n";
	my $value;
	foreach (sort keys %::Config) {
	    $value = $::Config{$_};
	    $value = '' unless defined $value;
	    $value =~ s/'/\\'/g;
	    print OUT "$_='$value'\n";
	}
    }
} # sub Dump

sub Edit {
    # Edit the report
    if ($usefile || $body) {
	my $description = "Please make sure that the name of the editor you want to use is correct.";
	my $entry = _prompt($description, 'Editor', $ed);
	$ed = $entry unless $entry eq '';
    }

    _edit_file($ed);
}

sub _edit_file {
    my $editor = shift;

    my $report_written = 0;

    while ( !$report_written ) {
        my $exit_status = system("$editor $filename");
        if ($exit_status) {
            my $desc = <<EOF;
The editor you chose ('$editor') could not be run!

If you mistyped its name, please enter it now, otherwise just press Enter.
EOF
            my $entry = _prompt( $desc, 'Editor', $editor );
            if ( $entry ne "" ) {
                $editor = $entry;
                next;
            } else {
                paraprint <<EOF;
You may want to save your report to a file, so you can edit and
mail it later.
EOF
                return;
            }
        }
        return if ( $ok and not $opt{n} ) || $body;

        # Check that we have a report that has some, eh, report in it.

        unless ( _fingerprint_lines_in_report() ) {
            my $description = <<EOF;
It looks like you didn't enter a report. You may [r]etry your edit
or [c]ancel this report.
EOF
            my $action = _prompt( $description, "Action (Retry/Cancel) " );
            if ( $action =~ /^[re]/i ) {    # <R>etry <E>dit
                next;
            } elsif ( $action =~ /^[cq]/i ) {    # <C>ancel, <Q>uit
                Cancel();                        # cancel exits
            }
        }
        # Ok. the user did what they needed to;
        return;

    }
}


sub Cancel {
    1 while unlink($filename);  # remove all versions under VMS
    print "\nQuitting without sending your message.\n";
    exit(0);
}

sub NowWhat {
    # Report is done, prompt for further action
    if( !$opt{S} ) {
	while(1) {
	    my $menu = <<EOF;


You have finished composing your message. At this point, you have 
a few options. You can:

    * [Se]nd the message to $address$andcc, 
    * [D]isplay the message on the screen,
    * [R]e-edit the message
    * Display or change the message's [su]bject
    * Save the message to a [f]ile to mail at another time
    * [Q]uit without sending a message

EOF
      retry:
        print $menu;
	    my $action =  _prompt('', "Action (Send/Display/Edit/Subject/Save to File)");;
        print "\n";
	    if ($action =~ /^(f|sa)/i) { # <F>ile/<Sa>ve
            if ( SaveMessage() ) { exit }
	    } elsif ($action =~ /^(d|l|sh)/i ) { # <D>isplay, <L>ist, <Sh>ow
		# Display the message
		open(REP, "<$filename") or die "Couldn't open file '$filename': $!\n";
		while (<REP>) { print $_ }
		close(REP) or die "Error closing report file '$filename': $!";
	    } elsif ($action =~ /^su/i) { # <Su>bject
		my $reply = _prompt( "Subject: $subject", "If the above subject is fine, press Enter. Otherwise, type a replacement now\nSubject");
		if ($reply ne '') {
		    unless (TrivialSubject($reply)) {
			$subject = $reply;
			print "Subject: $subject\n";
		    }
		}
	    } elsif ($action =~ /^se/i) { # <S>end
		# Send the message
		my $reply =  _prompt( "Are you certain you want to send this message?", 'Please type "yes" if you are','no');
		if ($reply =~ /^yes$/) {
		    last;
		} else {
		    paraprint <<EOF;
You didn't type "yes", so your message has not yet been sent.
EOF
		}
	    } elsif ($action =~ /^[er]/i) { # <E>dit, <R>e-edit
		# edit the message
		Edit();
	    } elsif ($action =~ /^[qc]/i) { # <C>ancel, <Q>uit
		Cancel();
	    } elsif ($action =~ /^s/i) {
		paraprint <<EOF;
The command you entered was ambiguous. Please type "send", "save" or "subject".
EOF
	    }
	}
    }
} # sub NowWhat

sub TrivialSubject {
    my $subject = shift;
    if ($subject =~
	/^(y(es)?|no?|help|perl( (bug|problem))?|bug|problem)$/i ||
	length($subject) < 4 ||
	$subject !~ /\s/) {
	print "\nThe subject you entered wasn't very descriptive. Please try again.\n\n";
        return 1;
    } else {
	return 0;
    }
}

sub SaveMessage {
    my $file_save = $outfile || "$progname.rep";
    my $file = _prompt( '', "Name of file to save message in", $file_save );
    save_message_to_disk($file) || return undef;
    print "\n";
    paraprint <<EOF;
A copy of your message has been saved in '$file' for you to
send to '$address' with your normal mail client.
EOF
}

sub Send {

    # Message has been accepted for transmission -- Send the message

    # on linux certain "mail" implementations won't accept the subject
    # as "~s subject" and thus the Subject header will be corrupted
    # so don't use Mail::Send to be safe
    eval {
        if ( $::HaveSend && !$Is_Linux && !$Is_OpenBSD ) {
            _send_message_mailsend();
        } elsif ($Is_VMS) {
            _send_message_vms();
        } else {
            _send_message_sendmail();
        }
    };

    if ( my $error = $@ ) {
        paraprint <<EOF;
$0 has detected an error while trying to send your message: $error.

Your message may not have been sent. You will now have a chance to save a copy to disk.
EOF
        SaveMessage();
        return;
    }

    1 while unlink($filename);    # remove all versions under VMS
}    # sub Send

sub Help {
    print <<EOF;

This program is designed to help you generate and send bug reports
(and thank-you notes) about perl5 and the modules which ship with it.

In most cases, you can just run "$0" interactively from a command
line without any special arguments and follow the prompts.

Advanced usage:

$0  [-v] [-a address] [-s subject] [-b body | -f inpufile ] [ -F outputfile ]
    [-r returnaddress] [-e editor] [-c adminaddress | -C] [-S] [-t] [-h]
$0  [-v] [-r returnaddress] [-A] [-ok | -okay | -nok | -nokay]


Options:

  -v    Include Verbose configuration data in the report
  -f    File containing the body of the report. Use this to
        quickly send a prepared message.
  -F    File to output the resulting mail message to, instead of mailing.
  -S    Send without asking for confirmation.
  -a    Address to send the report to. Defaults to '$address'.
  -c    Address to send copy of report to. Defaults to '$cc'.
  -C    Don't send copy to administrator.
  -s    Subject to include with the message. You will be prompted
        if you don't supply one on the command line.
  -b    Body of the report. If not included on the command line, or
        in a file with -f, you will get a chance to edit the message.
  -r    Your return address. The program will ask you to confirm
        this if you don't give it here.
  -e    Editor to use.
  -t    Test mode. The target address defaults to '$testaddress'.
  -T    Thank-you mode. The target address defaults to '$thanksaddress'.
  -d    Data mode.  This prints out your configuration data, without mailing
        anything. You can use this with -v to get more complete data.
  -A    Don't send a bug received acknowledgement to the return address.
  -ok   Report successful build on this system to perl porters
        (use alone or with -v). Only use -ok if *everything* was ok:
        if there were *any* problems at all, use -nok.
  -okay As -ok but allow report from old builds.
  -nok  Report unsuccessful build on this system to perl porters
        (use alone or with -v). You must describe what went wrong
        in the body of the report which you will be asked to edit.
  -nokay As -nok but allow report from old builds.
  -h    Print this help message.

EOF
}

sub filename {
    if ($::HaveTemp) {
	# Good. Use a secure temp file
	my ($fh, $filename) = File::Temp::tempfile(UNLINK => 1);
	close($fh);
	return $filename;
    } else {
	# Bah. Fall back to doing things less securely.
	my $dir = File::Spec->tmpdir();
	$filename = "bugrep0$$";
	$filename++ while -e File::Spec->catfile($dir, $filename);
	$filename = File::Spec->catfile($dir, $filename);
    }
}

sub paraprint {
    my @paragraphs = split /\n{2,}/, "@_";
    for (@paragraphs) {   # implicit local $_
	s/(\S)\s*\n/$1 /g;
	write;
	print "\n";
    }
}

sub _prompt {
    my ($explanation, $prompt, $default) = (@_);
    if ($explanation) {
        print "\n\n";
        paraprint $explanation;
    }
    print $prompt. ($default ? " [$default]" :''). ": ";
	my $result = scalar(<>);
    chomp($result);
	$result =~ s/^\s*(.*?)\s*$/$1/s;
    if ($default && $result eq '') {
        return $default;
    } else {
        return $result;
    }
}

sub _build_header {
    my %attr = (@_);

    my $head = '';
    for my $header (keys %attr) {
        $head .= "$header: ".$attr{$header}."\n";
    }
    return $head;
}

sub _message_headers {
    my %headers = ( To => $address, Subject => $subject );
    $headers{'Cc'}         = $cc        if ($cc);
    $headers{'Message-Id'} = $messageid if ($messageid);
    $headers{'Reply-To'}   = $from      if ($from);
    $headers{'From'}       = $from      if ($from);
    return \%headers;
}

sub build_complete_message {
    my $content = _build_header(%{_message_headers()}) . "\n\n";
    open( REP, "<$filename" ) or die "Couldn't open file '$filename': $!\n";
    while (<REP>) { $content .= $_; }
    close(REP) or die "Error closing report file '$filename': $!";
    return $content;
}

sub save_message_to_disk {
    my $file = shift;

	    open OUTFILE, ">$file" or do { warn  "Couldn't open '$file': $!\n"; return undef};
        print OUTFILE build_complete_message();
        close(OUTFILE) or do { warn  "Error closing $file: $!"; return undef };
	    print "\nMessage saved.\n";
        return 1;
}

sub _send_message_vms {
    if (   ( $address =~ /@/ and $address !~ /^\w+%"/ )
        or ( $cc =~ /@/ and $cc !~ /^\w+%"/ ) ) {
        my $prefix;
        foreach ( qw[ IN MX SMTP UCX PONY WINS ], '' ) {
            $prefix = "$_%", last if $ENV{"MAIL\$PROTOCOL_$_"};
        }
        $address = qq[${prefix}"$address"] unless $address =~ /^\w+%"/;
        $cc = qq[${prefix}"$cc"] unless !$cc || $cc =~ /^\w+%"/;
    }
    $subject =~ s/"/""/g;
    $address =~ s/"/""/g;
    $cc      =~ s/"/""/g;
    my $sts = system(qq[mail/Subject="$subject" $filename. "$address","$cc"]);
    if ($sts) {
        die "Can't spawn off mail (leaving bug report in $filename): $sts";
    }
}

sub _send_message_mailsend {
    my $msg = Mail::Send->new();
    my %headers = %{_message_headers()};
    for my $key ( keys %headers) {
        $msg->add($key => $headers{$key});
    }

    $fh = $msg->open;
    open(REP, "<$filename") or die "Couldn't open '$filename': $!\n";
    while (<REP>) { print $fh $_ }
    close(REP) or die "Error closing $filename: $!";
    $fh->close or die "Error sending mail: $!";

    print "\nMessage sent.\n";
}

sub _probe_for_sendmail {
    my $sendmail = "";
    for (qw(/usr/lib/sendmail /usr/sbin/sendmail /usr/ucblib/sendmail)) {
        $sendmail = $_, last if -e $_;
    }
    if ( $^O eq 'os2' and $sendmail eq "" ) {
        my $path = $ENV{PATH};
        $path =~ s:\\:/:;
        my @path = split /$Config{'path_sep'}/, $path;
        for (@path) {
            $sendmail = "$_/sendmail",     last if -e "$_/sendmail";
            $sendmail = "$_/sendmail.exe", last if -e "$_/sendmail.exe";
        }
    }
    return $sendmail;
}

sub _send_message_sendmail {
    my $sendmail = _probe_for_sendmail();
    unless ($sendmail) {
        my $message_start = !$Is_Linux && !$Is_OpenBSD ? <<'EOT' : <<'EOT';
It appears that there is no program which looks like "sendmail" on
your system and that the Mail::Send library from CPAN isn't available.
EOT
It appears that there is no program which looks like "sendmail" on
your system.
EOT
        paraprint(<<"EOF"), die "\n";
$message_start
Because of this, there's no easy way to automatically send your
message.

A copy of your message has been saved in '$filename' for you to
send to '$address' with your normal mail client.
EOF
    }

    open( SENDMAIL, "|-", $sendmail, "-t", "-oi", "-f", $from )
        || die "'|$sendmail -t -oi -f $from' failed: $!";
    print SENDMAIL build_complete_message();
    if ( close(SENDMAIL) ) {
        print "\nMessage sent\n";
    } else {
        warn "\nSendmail returned status '", $? >> 8, "'\n";
    }
}



# a strange way to check whether any significant editing
# has been done: check whether any new non-empty lines
# have been added.

sub _fingerprint_lines_in_report {
    my $new_lines = 0;
    # read in the report template once so that
    # we can track whether the user does any editing.
    # yes, *all* whitespace is ignored.

    open(REP, "<$filename") or die "Unable to open report file '$filename': $!\n";
    while (my $line = <REP>) {
        $line =~ s/\s+//g;
        $new_lines++ if (!$REP{$line});

    }
    close(REP) or die "Error closing report file '$filename': $!";
    # returns the number of lines with content that wasn't there when last we looked
    return $new_lines;
}



format STDOUT =
^<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< ~~
$_
.

__END__

=head1 NAME

perlbug - how to submit bug reports on Perl

=head1 SYNOPSIS

B<perlbug>

B<perlbug> S<[ B<-v> ]> S<[ B<-a> I<address> ]> S<[ B<-s> I<subject> ]>
S<[ B<-b> I<body> | B<-f> I<inputfile> ]> S<[ B<-F> I<outputfile> ]>
S<[ B<-r> I<returnaddress> ]>
S<[ B<-e> I<editor> ]> S<[ B<-c> I<adminaddress> | B<-C> ]>
S<[ B<-S> ]> S<[ B<-t> ]>  S<[ B<-d> ]>  S<[ B<-A> ]>  S<[ B<-h> ]> S<[ B<-T> ]>

B<perlbug> S<[ B<-v> ]> S<[ B<-r> I<returnaddress> ]>
 S<[ B<-A> ]> S<[ B<-ok> | B<-okay> | B<-nok> | B<-nokay> ]>

B<perlthanks>

=head1 DESCRIPTION


This program is designed to help you generate and send bug reports
(and thank-you notes) about perl5 and the modules which ship with it.

In most cases, you can just run it interactively from a command
line without any special arguments and follow the prompts.

If you have found a bug with a non-standard port (one that was not
part of the I<standard distribution>), a binary distribution, or a
non-core module (such as Tk, DBI, etc), then please see the
documentation that came with that distribution to determine the
correct place to report bugs.

If you are unable to send your report using B<perlbug> (most likely
because your system doesn't have a way to send mail that perlbug
recognizes), you may be able to use this tool to compose your report
and save it to a file which you can then send to B<perlbug@perl.org>
using your regular mail client.

In extreme cases, B<perlbug> may not work well enough on your system
to guide you through composing a bug report. In those cases, you
may be able to use B<perlbug -d> to get system configuration
information to include in a manually composed bug report to
B<perlbug@perl.org>.


When reporting a bug, please run through this checklist:

=over 4

=item What version of Perl you are running?

Type C<perl -v> at the command line to find out.

=item Are you running the latest released version of perl?

Look at http://www.perl.org/ to find out.  If you are not using the
latest released version, please try to replicate your bug on the
latest stable release.

Note that reports about bugs in old versions of Perl, especially
those which indicate you haven't also tested the current stable
release of Perl, are likely to receive less attention from the
volunteers who build and maintain Perl than reports about bugs in
the current release.

This tool isn't appropriate for reporting bugs in any version
prior to Perl 5.0.

=item Are you sure what you have is a bug?

A significant number of the bug reports we get turn out to be
documented features in Perl.  Make sure the issue you've run into
isn't intentional by glancing through the documentation that comes
with the Perl distribution.

Given the sheer volume of Perl documentation, this isn't a trivial
undertaking, but if you can point to documentation that suggests
the behaviour you're seeing is I<wrong>, your issue is likely to
receive more attention. You may want to start with B<perldoc>
L<perltrap> for pointers to common traps that new (and experienced)
Perl programmers run into.

If you're unsure of the meaning of an error message you've run
across, B<perldoc> L<perldiag> for an explanation.  If the message
isn't in perldiag, it probably isn't generated by Perl.  You may
have luck consulting your operating system documentation instead.

If you are on a non-UNIX platform B<perldoc> L<perlport>, as some
features may be unimplemented or work differently.

You may be able to figure out what's going wrong using the Perl
debugger.  For information about how to use the debugger B<perldoc>
L<perldebug>.

=item Do you have a proper test case?

The easier it is to reproduce your bug, the more likely it will be
fixed -- if nobody can duplicate your problem, it probably won't be 
addressed.

A good test case has most of these attributes: short, simple code;
few dependencies on external commands, modules, or libraries; no
platform-dependent code (unless it's a platform-specific bug);
clear, simple documentation.

A good test case is almost always a good candidate to be included in
Perl's test suite.  If you have the time, consider writing your test case so
that it can be easily included into the standard test suite.

=item Have you included all relevant information?

Be sure to include the B<exact> error messages, if any.
"Perl gave an error" is not an exact error message.

If you get a core dump (or equivalent), you may use a debugger
(B<dbx>, B<gdb>, etc) to produce a stack trace to include in the bug
report.  

NOTE: unless your Perl has been compiled with debug info
(often B<-g>), the stack trace is likely to be somewhat hard to use
because it will most probably contain only the function names and not
their arguments.  If possible, recompile your Perl with debug info and
reproduce the crash and the stack trace.

=item Can you describe the bug in plain English?

The easier it is to understand a reproducible bug, the more likely
it will be fixed.  Any insight you can provide into the problem
will help a great deal.  In other words, try to analyze the problem
(to the extent you can) and report your discoveries.

=item Can you fix the bug yourself?

A bug report which I<includes a patch to fix it> will almost
definitely be fixed.  When sending a patch, please use the C<diff>
program with the C<-u> option to generate "unified" diff files.
Bug reports with patches are likely to receive significantly more
attention and interest than those without patches.

Your patch may be returned with requests for changes, or requests for more
detailed explanations about your fix.

Here are a few hints for creating high-quality patches:

Make sure the patch is not reversed (the first argument to diff is
typically the original file, the second argument your changed file).
Make sure you test your patch by applying it with the C<patch>
program before you send it on its way.  Try to follow the same style
as the code you are trying to patch.  Make sure your patch really
does work (C<make test>, if the thing you're patching is covered
by Perl's test suite).

=item Can you use C<perlbug> to submit the report?

B<perlbug> will, amongst other things, ensure your report includes
crucial information about your version of perl.  If C<perlbug> is
unable to mail your report after you have typed it in, you may have
to compose the message yourself, add the output produced by C<perlbug
-d> and email it to B<perlbug@perl.org>.  If, for some reason, you
cannot run C<perlbug> at all on your system, be sure to include the
entire output produced by running C<perl -V> (note the uppercase V).

Whether you use C<perlbug> or send the email manually, please make
your Subject line informative.  "a bug" is not informative.  Neither
is "perl crashes" nor is "HELP!!!".  These don't help.  A compact
description of what's wrong is fine.

=item Can you use C<perlbug> to submit a thank-you note?

Yes, you can do this by either using the C<-T> option, or by invoking
the program as C<perlthanks>. Thank-you notes are good. It makes people
smile. 

=back

Having done your bit, please be prepared to wait, to be told the
bug is in your code, or possibly to get no reply at all.  The
volunteers who maintain Perl are busy folks, so if your problem is
an obvious bug in your own code, is difficult to understand or is
a duplicate of an existing report, you may not receive a personal
reply.

If it is important to you that your bug be fixed, do monitor the
perl5-porters@perl.org mailing list and the commit logs to development
versions of Perl, and encourage the maintainers with kind words or
offers of frosty beverages.  (Please do be kind to the maintainers.
Harassing or flaming them is likely to have the opposite effect of
the one you want.)

Feel free to update the ticket about your bug on http://rt.perl.org
if a new version of Perl is released and your bug is still present.

=head1 OPTIONS

=over 8

=item B<-a>

Address to send the report to.  Defaults to B<perlbug@perl.org>.

=item B<-A>

Don't send a bug received acknowledgement to the reply address.
Generally it is only a sensible to use this option if you are a
perl maintainer actively watching perl porters for your message to
arrive.

=item B<-b>

Body of the report.  If not included on the command line, or
in a file with B<-f>, you will get a chance to edit the message.

=item B<-C>

Don't send copy to administrator.

=item B<-c>

Address to send copy of report to.  Defaults to the address of the
local perl administrator (recorded when perl was built).

=item B<-d>

Data mode (the default if you redirect or pipe output).  This prints out
your configuration data, without mailing anything.  You can use this
with B<-v> to get more complete data.

=item B<-e>

Editor to use.

=item B<-f>

File containing the body of the report.  Use this to quickly send a
prepared message.

=item B<-F>

File to output the results to instead of sending as an email. Useful
particularly when running perlbug on a machine with no direct internet
connection.

=item B<-h>

Prints a brief summary of the options.

=item B<-ok>

Report successful build on this system to perl porters. Forces B<-S>
and B<-C>. Forces and supplies values for B<-s> and B<-b>. Only
prompts for a return address if it cannot guess it (for use with
B<make>). Honors return address specified with B<-r>.  You can use this
with B<-v> to get more complete data.   Only makes a report if this
system is less than 60 days old.

=item B<-okay>

As B<-ok> except it will report on older systems.

=item B<-nok>

Report unsuccessful build on this system.  Forces B<-C>.  Forces and
supplies a value for B<-s>, then requires you to edit the report
and say what went wrong.  Alternatively, a prepared report may be
supplied using B<-f>.  Only prompts for a return address if it
cannot guess it (for use with B<make>). Honors return address
specified with B<-r>.  You can use this with B<-v> to get more
complete data.  Only makes a report if this system is less than 60
days old.

=item B<-nokay>

As B<-nok> except it will report on older systems.

=item B<-r>

Your return address.  The program will ask you to confirm its default
if you don't use this option.

=item B<-S>

Send without asking for confirmation.

=item B<-s>

Subject to include with the message.  You will be prompted if you don't
supply one on the command line.

=item B<-t>

Test mode.  The target address defaults to B<perlbug-test@perl.org>.

=item B<-T>

Send a thank-you note instead of a bug report. 

=item B<-v>

Include verbose configuration data in the report.

=back

=head1 AUTHORS

Kenneth Albanowski (E<lt>kjahds@kjahds.comE<gt>), subsequently
I<doc>tored by Gurusamy Sarathy (E<lt>gsar@activestate.comE<gt>),
Tom Christiansen (E<lt>tchrist@perl.comE<gt>), Nathan Torkington
(E<lt>gnat@frii.comE<gt>), Charles F. Randall (E<lt>cfr@pobox.comE<gt>),
Mike Guy (E<lt>mjtg@cam.a.ukE<gt>), Dominic Dunlop
(E<lt>domo@computer.orgE<gt>), Hugo van der Sanden (E<lt>hv@crypt.org<gt>),
Jarkko Hietaniemi (E<lt>jhi@iki.fiE<gt>), Chris Nandor
(E<lt>pudge@pobox.comE<gt>), Jon Orwant (E<lt>orwant@media.mit.eduE<gt>,
Richard Foley (E<lt>richard.foley@rfi.netE<gt>), and Jesse Vincent
(E<lt>jesse@bestpractical.com<gt>).

=head1 SEE ALSO

perl(1), perldebug(1), perldiag(1), perlport(1), perltrap(1),
diff(1), patch(1), dbx(1), gdb(1)

=head1 BUGS

None known (guess what must have been used to report them?)

=cut


ページが見つかりませんでした – 京都の外壁塗装で選ぶべき評判・口コミの良い業者ランキング

京都の外壁塗装業者ランキング
京都の外壁塗装業者を評判・口コミから厳選

京都の外壁塗装業者を徹底調査!

京都で評判の良いおすすめ外壁塗装業者ランキング!

京都で評判・口コミの良い外壁塗装業者ランキング!

こんにちは、「京都のおすすめ外壁塗装業者を実績・評判から厳選して10社ご紹介」の管理人です。
この度は当サイトをご覧いただきき、本当にありがとうございます。

このサイトでは、京都で生まれ育った管理人である私が、地元である京都の優良外壁塗装業者をご紹介しています。
京都にお住まいの方で、外壁塗装を検討されている方にとって少しでもお役に立てれば幸いです。

まず、なぜ私が「京都の優良外壁塗装業者」を紹介しようと思ったのか? 手短にご説明させていただきます。

実は最近、たくさんの思い出が詰まった我が家の外壁塗装工事を行いました。

築年数は約20年程。 築20年を超えたくらいのタイミングで塗り替えをしないと家の寿命が短くなってしまうと聞いたこと。
そして何より、この20年一切外壁には手をかけていなかったので、汚れが目立ち美観がすごく悪くなっていたこと。
これが初めて外壁塗装の塗り替えを検討するきっかけとなりました。

私は性格的に凝り性で、何でも自分で調べないと気が済まない性格です。
自分が納得するまで徹底的に調査して、どこよりも良い塗装業者さんを見つけて塗り替えをしてもらおう!と意気込みました。

幸いにも、私は職業柄、そして長年京都に住み続けていることもあり、建築関係(大工さん・建築士さん・設計士さんなど)の知人が複数います。
実際に行った調査方法として、その建築関係の知人と直接会い、徹底的に塗装業界を含む建築業界の生の声を聞き込みました。

その結果、納得・安心して塗り替えをお願いできる塗装業者さんと出会うことができ、仕上がり・工事金額ともに満足のいく塗り替えをすることができました。

私と同じように、

・大切な家だからこそ、丁寧にしっかりと外壁塗装をしてほしい
・少しでも安くなれば嬉しいけど、手抜き工事はされたくない
・しっかり工事内容を説明してくれるような、信頼できる塗装業者を見つけたい

とお考えの方は、きっとこのサイトが京都での塗装業者探しの参考になると信じております。

ぜひ、京都にお住まいの方で、外壁塗装を検討されている方、優良塗装業者をお探しの方の参考にしてください。

京都で信頼できる外壁塗装業者を選ぶポイント

京都で信頼できる外壁塗装業者を選ぶポイント

今回、私が「優良外壁塗装業者の定義」として挙げたポイントは以下の3点です。

① 良心的な外壁塗装の金額設定
② 塗り替えの施工技術のレベルが高い
③ 対応品質・サポートがしっかりしている

恐らく皆さんにとっても、上記3点が揃っていれば優良塗装業者と言えるでしょう。
しかし、京都にも外壁塗装業者は数多くありますが、上記全てを満たす塗装業者というのは実は非常に少ないのです。

「値段が安くても、塗装工事自体の品質が悪い」
「仕上がりはすごく良いけど、工事金額が相場より明らかに高額」
「会社の規模は大きいが、施工は全て下請けに丸投げで対応が雑or下請け任せ」
など、どれか1つの項目は満たしても、他のポイントが良くないという塗装業者が圧倒的に多いのが現状です。

それでは、「優良外壁塗装業者の定義」をもう少し掘り下げてご説明します。

良心的な外壁塗装工事の金額設定

良心的な外壁塗装工事の金額設定

良心的な金額設定は、やはり皆さん重視したいポイントではないでしょうか?
私自身もここは絶対に外せないポイントでした。

一般的な戸建住宅の外壁塗装の価格相場は、おおよそ80万〜120万円とされています。
しかし、ただ安ければ良いという訳でない、施工品質が伴わないといけない、というのが難しいポイントです。

良心的な工事金額、その中で最大限高品質な塗り替えを行ってくれる塗装業者を見極めるポイント
それは、

営業マンやCM・チラシなど、過剰な営業費・宣伝広告費を使っていないかどうか、です。

外壁塗装業界は、大手メーカーから地元密着型の小さな塗装業者まで、お客さんの奪い合い状態となっています。
そのため、多くの塗装業者が他社より少しでも知名度を上げるため、少しでも多くのお客さんに知ってもらうために、多額の営業費・宣伝広告費を使っています。
大手メーカーであればCM、小さな塗装業者でも新聞チラシ、そして多くの営業マンを雇い、訪問販売による営業活動を行なっているのです。

もちろん塗装業者も生活がかかっているので、営業・宣伝を行い、少しでも仕事を受注しようとするのは当然です。
しかし問題は、多額の営業費・宣伝広告費は皆さんがお支払いになる工事代金に含まれる、という点です。

過剰な営業費・宣伝広告費を使っている塗装業者は、総じて塗り替えの工事金額が高額になりがちです。
こうなると、「なぜ私たちが工事には直接関係の無い営業費・宣伝広告費を支払わないといけないのか」と思ってしまいますよね。

本当に優良な塗装業者なら、広告を出したり営業マンを雇ったりしなくても評判・口コミでお客さんは自然と集まるのです。
ただでさえ価格相場の幅が広く、工事金額の内訳がわかりにくい外壁塗装です。
気になった塗装業者が、営業マンを雇っていないか、過剰な広告を出していないか、確認してみましょう。

塗り替えの施工技術のレベルが高い

塗り替えの施工技術のレベルが高い

施工技術・施工品質に関しては、気にはなりますがわかりにくいポイントです。
私もそうでしたが、普段塗装工事に馴染みが無い一般の方からすれば、実際に施工している姿を見ても、技術の良し悪しを見極めるのは難しいのです。

ここで1つの見極めポイントとなるのが、「一級塗装技能士」という資格です。

この「一級塗装技能士」は、塗装の実技試験と学科試験の両方に合格した塗装職人のみが持っている資格になります。
もちろんこれは国家資格です

資格を持っていない塗装職人さんでも、技術力が高い職人さんは沢山いらっしゃると思いますが、少なくともこの資格を持つ塗装職人さんは、一定水準以上の技術・知識を持つ塗装職人だと国から認められているのです。
気になった塗装業者に「一級塗装技能士」の取得者がいるのか、ぜひ確認しておきましょう。

塗装工事以外にも接客対応・サポートがしっかりしている

塗装工事以外にも対応・サポートがしっかりしている

外壁塗装を検討されている方の中で、外壁塗装について精通してるという方は少ないと思います。
なぜなら、外壁塗装の塗り替え周期は10~20年に一度、知らなくても当然なのです。
むしろ私のように、「初めて外壁塗装を検討している」という人の方が多いかもしれません。

一般の方が馴染みが薄い外壁塗装工事だからこそ、対応品質・サポートがしっかりしている塗装業者の方が安心して施工を任せられるでしょう。

打ち合わせや現地調査、見積もりの段階で、「わからないことはないか?心配な点はないか?」など、気遣ってくれる塗装業者は本当に心強いです。
初めて塗り替え工事を行う方なら、尚更安心して工事を任せることができます。
こちらの些細な疑問・質問にも、丁寧にしっかり対応してくれる塗装業者を選ぶようにしましょう。

また、不思議と対応品質が良い塗装業者は、総じて塗り替えの施工品質も高いです。
やはり、真面目に誠実に塗装と向き合っている業者は、その真面目さ・誠実さが対応品質にも現れるということですね。

京都で評判の良い外壁塗装業者はどこ?

京都で評判の良い外壁塗装業者はどこ?

以上のことを踏まえた上で私は、複数の塗装業者から見積もりをいただき、じっくりと見積書を比較検討し、塗装業者を吟味しました。
そしてその結果、京都の中でも大変素晴らしい外壁塗装業者さんと出会うことができ、仕上がり・価格ともに満足のいく外壁塗装工事をしていただくことができました。

ここでは、私が実際に塗り替えを依頼した塗装業者さんをはじめ、

・見積もりを依頼したり問い合わせたりした際に「3つの優良外壁塗装業者の定義を満たしている」と感じた塗装業者さん
・建築業界に在籍している知人の中で評判の良い塗装業者さん

この2点を含めた、京都で安心して塗装工事を任せることができる優良外壁塗装業者さんをランキング形式でご紹介させていただきます。

ぜひ京都にお住まいの方は、優良外壁塗装業者探しの参考にしてください。

京都で評判・口コミの良い外壁塗装業者ランキング
ランキング1位

京都で評判・口コミの良い外壁塗装業者ランキング

株式会社ウェルビーホーム

京都でおすすめの優良外壁塗装業者|株式会社ウェルビーホーム

株式会社ウェルビーホームさんの特徴

今回、私が実際に外壁塗装の塗り替えを依頼し、最も皆さんにもおすすめしたい外壁塗装業者さんは、「株式会社ウェルビーホーム」さんです。

ウェルビーホームさんは、代表の高橋さんが直接打ち合わせ・現場調査から実際の施工、そして工事後のアフターフォローまで全て対応してくれます。
また、高橋さんは建築士の資格も持っており、外壁塗装だけでなく住まいのこと全般に精通しておられるので、様々な観点から外壁塗装に関するアドバイスをしてくれます。
高橋さん自身とても笑顔の素敵な物腰の優しい方で、外壁塗装以外の住まいに関する質問にも、とてもわかりやすく丁寧に答えてくださいました。

見積書も、他のどの業者さんよりも丁寧で詳細に作ってくださり、工事内容が非常に明確で安心できたのがウェルビーホームさんを選んだ大きなポイントです。
さらに、ウェルビーホームさんは「一級塗装技能士」の資格を所持する職人さんが在籍しています。
施工してくれた職人さん方もとても愛想良くマナーもしっかりしており、塗り替えの仕上がり・接客応対ともに大満足の結果でした。

工事金額も他業者さんと比べても安価でしたし、是非とも京都で外壁塗装を検討されている方におすすめしたい優良塗装業者さんです。

株式会社ウェルビーホームさんを利用した方の評判・口コミ

40代・女性・京都市中京区在住

外壁塗装が初めての私にも非常に丁寧にご説明くださいました。
打ち合わせの時点から高橋社長の人柄の良さは伝わりました。
見積書の内容も細かく教えてくださり、初めての外壁塗装も安心して行えました、ありがとうございました。

50代・男性・京都府城陽市在住

問い合わせから施工までやりとりがとてもスムーズでした。
特に問い合わせから現地確認までの対応の早さは一番でした。
カラーシミュレーションなど、色決めも早かったです。
仕上がりも綺麗で大満足です。

50代・女性・大阪府寝屋川市在住

前回の工事代金より大幅に安かったので大変驚きました。
こんなことなら前回の塗装工事もウェルビーホームさんにお願いしたかったです。
次回の塗装もお願いしたいので、その際はよろしくお願いします。

京都で評判・口コミの良い外壁塗装業者ランキング
ランキング2位

京都で評判・口コミの良い外壁塗装業者ランキング

株式会社 佐藤塗装店

京都でおすすめの優良外壁塗装業者|株式会社 佐藤塗装店

株式会社 佐藤塗装店さんの特徴

「株式会社 佐藤塗装店」さんは、京都市西京区を中心に京都府全域、大阪府、滋賀県、奈良県と幅広いエリアで活躍する塗装業者さんです。

代表の佐藤さんは、「一級塗装技能士」の資格をはじめ、「一級左官技能士」「足場組立作業主任者」など、数多くの資格を有しておられます。
塗り替えを依頼する塗装業者さんが塗装だけでなく他の建築工事に関して精通していると、幅広い視点で的確なアドバイスをもらえるので嬉しいポイントです。

佐藤塗装店さんは、日本ペイント株式会社の特約店であり、使用する塗料も日本ペイントが主になりますので、塗料の単価や性能など、工事内容が非常に明確です。
見積もりの内容も分かりやすく明瞭会計で、職人さんの対応も非常に丁寧です。
京都の数ある塗装業者の中でも、5指に入る優良塗装業者さんです。

株式会社 佐藤塗装店さんを利用した方の評判・口コミ

50代・男性・京都市西京区在住

日本ペイントの塗料と聞いて安心しましたし、塗料の知識が豊富な営業さんで、勉強になりました。
価格がわかりやすく、日本ペイントの塗料を使用しているとのことで、決めました。
仕上がりにも大変満足です。

50代・女性・兵庫県神戸市在住

住まいのイメージを変えたく、相談に乗っていただきました。
熱心に対応して頂き、次回もお願いしたいと思います。
ありがとうございました。

40代・女性・大阪府堺市在住

塗装後玄関周りの色が気に入らず、再度塗り替えて頂き有難うございました。
大満足です。ご近所様をご紹介させて頂きます。

京都で評判・口コミの良い外壁塗装業者ランキング
ランキング3位

京都で評判・口コミの良い外壁塗装業者ランキング

株式会社 伊藤建装

京都でおすすめの優良外壁塗装業者|株式会社 伊藤建装

株式会社 伊藤建装さんの特徴

「株式会社 伊藤建装」さんは、京都市伏見区を中心に京都府・滋賀県・大阪府北部で活躍する塗装業者さんです。

「一級塗装技能士」の資格保有者だけでなく、外壁診断士や外壁アドバイザーなどの資格保有者が複数在籍しておられ、まさに外壁のプロフェッショナルです。
非常に多くの塗料・プランをご用意されており、外壁診断士さんがお住まい一軒一軒に合ったプランを提案してくれます。

非常に多くの職人さんが在籍され、宣伝・広告にも力を入れておられるので、工事金額自体は決して安価ではありません
しかし、外壁をしっかり診断してほしい・質の良い塗装工事をしてほしいといった、金額より施工品質重視の方にはおすすめの塗装業者さんです。

株式会社 伊藤建装さんを利用した方の評判・口コミ

40代・女性・京都市左京区在住

職人さん達はゴミの片付けもきっちりされていて良かったと思います。
女性の職人さんがいらっしゃったので驚きました。
足場を組む時なども男性と変わらない力強さで仕事をこなされていたので感心してました。

40代・男性・京都市西京区在住

細かいところまで綺麗にして頂き、ありがとうございました。
工事中、台風が来た時には困りましたが、結果的に綺麗に仕上げてくださり満足です。

50代・男性・滋賀県大津市在住

見積もりから施工まで、こまかいこだわりを重視してくださりありがとうございました。
家が生まれ変わったように綺麗になり感謝しています。
丁寧な職人さん達にも感謝です。

京都で評判・口コミの良い外壁塗装業者ランキング

京都でのおすすめ優良外壁塗装業者
1位:株式会社ウェルビーホーム
京都で評判・口コミの良い外壁塗装業者ランキング|株式会社ウェルビーホーム
京都でのおすすめ優良外壁塗装業者
2位:株式会社 佐藤塗装店
京京都で評判・口コミの良い外壁塗装業者ランキング|株式会社 佐藤塗装店
京都でのおすすめ優良外壁塗装業者
3位:株式会社 伊藤建装
京都で評判・口コミの良い外壁塗装業者ランキング|株式会社 伊藤建装

【免責事項】当サイトは、管理人が個人的に情報収集した内容を基に作成しています。最新の情報は各サイトにお問い合わせください。

© 京都の外壁塗装で選ぶべき評判・口コミの良い業者ランキング.