maintenance/symlink_script.pl

   1 #!/usr/bin/perl
   2 use Module::Build;
   3 use strict;
   4 use warnings;
   5
   6 my $build = Module::Build->current;
   7
   8 my %symlink_scripts = ('bp_bulk_load_gff.pl' => 'bp_pg_bulk_load_gff.pl');
   9
  10 #my $blib_dir = File::Spec->catdir($build->blib, 'script');
  11 # using blib prior to installation, post build, always 'works', but the
  12 # installation process installs the symlink as the actual file, so we may as
  13 # well have just done a copy
  14
  15 my $install_dir = $build->install_destination('script');
  16 $build->log_info("Will try to install symlinks to $install_dir\n");
  17 my $orig_dir = $build->cwd;
  18 chdir($install_dir);
  19
  20 while (my ($source, $destination) = each %symlink_scripts) {
  21     eval { symlink($source, $destination) };
  22     $build->log_warn("Cannot create symbolic link named $destination on your system for $source in $install_dir\n") if $@;
  23 }
  24
  25 chdir($orig_dir);
  26
  27 exit;
  28
  29 __END__
  30
  31 =head1 NAME
  32
  33 symlink_script.pl - install script to create symbolic links
  34
  35 =head1 SYNOPSIS
  36
  37   perl Build.pl
  38   ./Build install
  39
  40 =head1 DESCRIPTION
  41
  42 Used during "./Build install". Only works if the script installation directory
  43 used during "perl Build.pl" matches that used for the actual installation during
  44 "./Build install". So if you install to a special place, do
  45
  46 perl Build.pl --install_base /home/me
  47 ./Build install
  48
  49 not
  50
  51 perl Build.pl
  52 ./Build install --install_base /home/me
  53
  54 This script will create a symlink to a script in that same directory. It was
  55 written to create a symlink with the name 'bp_pg_bulk_load_gff.pl' that targeted
  56 'bp_bulk_load_gff.pl' but can be extended by adding files to the
  57 %symlink_scripts hash.
  58
  59 Perl function 'symlink' is used to keep the script from crashing on systems
  60 that don't allow symbolic linking.
  61
  62 =head1 SEE ALSO
  63
  64 =cut
  65
  66 =head1 FEEDBACK
  67
  68 =head2 Mailing Lists
  69
  70 User feedback is an integral part of the evolution of this and other
  71 Bioperl modules. Send your comments and suggestions preferably to
  72 the Bioperl mailing list.  Your participation is much appreciated.
  73
  74   bioperl-l@bioperl.org                  - General discussion
  75   http://bioperl.org/wiki/Mailing_lists  - About the mailing lists
  76
  77 =head2 Reporting Bugs
  78
  79 Report bugs to the Bioperl bug tracking system to help us keep track
  80 of the bugs and their resolution. Bug reports can be submitted via the
  81 web:
  82
  83   http://bugzilla.open-bio.org/
  84
  85 =head1 AUTHOR - Sendu Bala
  86
  87 Email bix@sendu.me.uk
  88
  89 =cut