libproc-invokeeditor-perl 1.13-1 source package in Ubuntu


libproc-invokeeditor-perl (1.13-1) unstable; urgency=medium

  [ Salvatore Bonaccorso ]
  * Update Vcs-Browser URL to cgit web frontend
  * debian/control: Use HTTPS transport protocol for Vcs-Git URI

  [ gregor herrmann ]
  * debian/copyright: change Copyright-Format 1.0 URL to HTTPS.
  * Remove Jay Bonci from Uploaders. Thanks for your work!

  [ Florian Schlichting ]
  * Import upstream version 1.13
  * Add upstream metadata
  * Update copyright years
  * Drop Test::Pod build dependencies (author tests)
  * Bump dh compat to level 9
  * Add myself to Uploaders
  * Declare compliance with Debian Policy 4.1.1

 -- Florian Schlichting <email address hidden>  Wed, 15 Nov 2017 21:53:20 +0100

Upload details

Uploaded by:
Debian Perl Group on 2017-11-16
Uploaded to:
Original maintainer:
Debian Perl Group
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Groovy release on 2020-04-24 universe perl
Focal release on 2019-10-18 universe perl
Bionic release on 2017-11-17 universe perl


Bionic: [FULLYBUILT] amd64


File Size SHA-256 Checksum
libproc-invokeeditor-perl_1.13-1.dsc 2.2 KiB a417b69fa822fad8b1959c3b4505ba3a3031840aec79c81ebdc4021b3de96548
libproc-invokeeditor-perl_1.13.orig.tar.gz 13.7 KiB 4a2dbe1cd1c82c31f2bb9f3e417f0b04fadc171590df15330109c33d4d208175
libproc-invokeeditor-perl_1.13-1.debian.tar.xz 3.5 KiB 3570fd835b3e3545436d7a20c6d0b0237973a71d1e30698a112b8a780055cd26

Available diffs

No changes file available.

Binary packages built by this source

libproc-invokeeditor-perl: Perl extension for starting a text editor

 Proc::InvokeEditor module provides the ability to supply some text to an
 external text editor, have it edited by the user, and retrieve the results.
 The File::Temp module is used to provide secure, safe temporary
 files, and File::Temp is set to its highest available level of
 security. This may cause problems on some systems where no secure
 temporary directory is available.
 When the editor is started, no subshell is used. Your path will
 be scanned to find the binary to use for each editor if the string
 given does not exist as a file, and if a named editor contains whitespace,
 for example if you try to use the editor 'xemacs -nw', then the string will
 be split on whitespace and anything after the editor name will be passed
 as arguments to your editor. A shell is not used but this should cover
 most simple cases.