Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #210554 > unrolled thread

Debian Perl or Brew Perl for production application?

Back to article view | Back to linux.debian.user

Contents

  Debian Perl or Brew Perl for production application? Didar Hossain <didar.hossain@gmail.com> - 2019-07-01 18:30 +0200
    Re: Debian Perl or Brew Perl for production application? Jonas Smedegaard <jonas@jones.dk> - 2019-07-01 18:40 +0200
      Re: Debian Perl or Brew Perl for production application? Nicholas Geovanis <nickgeovanis@gmail.com> - 2019-07-01 19:00 +0200
    Re: Debian Perl or Brew Perl for production application? <tomas@tuxteam.de> - 2019-07-01 18:40 +0200
      Re: Debian Perl or Brew Perl for production application? Dave Sherohman <dave@sherohman.org> - 2019-07-02 12:00 +0200
        Re: Debian Perl or Brew Perl for production application? Alex Mestiashvili <amestia@rsh2.donotuse.de> - 2019-07-02 13:40 +0200
          [RESOLVED/Thanks] Re: Debian Perl or Brew Perl for production  application? Didar Hossain <didar.hossain@gmail.com> - 2019-07-04 09:40 +0200

#210554 — Debian Perl or Brew Perl for production application?

Hi,

I am developing a perl application to be deployed on a production Debian Stable
VM. So far, my approach has been to use the debian perl packages (perl modules) and
stay within those facilities. I am the sole system operator and wannabe
developer, there are no teams of sysadmins or developers.

Do you guys who run production debian stable servers use the debian perl
packages or use something like PerlBrew? I asked this question on #perl IRC and
they answered "PerlBrew/plenv/perl-build" - I want some experienced opinions
from the debian community as well.

Regards,
Didar

-- 
All international orders must be accompanied by payment in U. S. funds.

[toc] | [next] | [standalone]

#210556

[Multipart message — attachments visible in raw view] — view raw

Hi Didar,

Quoting Didar Hossain (2019-07-01 18:22:18)
> I am developing a perl application to be deployed on a production 
> Debian Stable VM. So far, my approach has been to use the debian perl 
> packages (perl modules) and stay within those facilities. I am the 
> sole system operator and wannabe developer, there are no teams of 
> sysadmins or developers.
> 
> Do you guys who run production debian stable servers use the debian 
> perl packages or use something like PerlBrew? I asked this question on 
> #perl IRC and they answered "PerlBrew/plenv/perl-build" - I want some 
> experienced opinions from the debian community as well.

I do a bit of perl programming (am JONASS on CPAN) and am a Debian 
developer as well.

I use cpanm occationally on my developer laptop, but on production 
servers I only use Debian packages.  I might "cheat" and install 
backported packages or even unofficial .deb packages, but never 
"side-installed" code on production servers.  Reason is that I want a 
single place to keep track of all code installed on the system: APT.

You might consider ask your question at the debian-perl mailinglist, as 
you are more likely to reach Perl folks there, I guess.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

[toc] | [prev] | [next] | [standalone]

#210558

[Multipart message — attachments visible in raw view] — view raw

I have worked in a couple places that prefer ActiveState perl.
https://www.activestate.com/products/activeperl/

On Mon, Jul 1, 2019, 11:37 AM Jonas Smedegaard <jonas@jones.dk> wrote:

> Hi Didar,
>
> Quoting Didar Hossain (2019-07-01 18:22:18)
> > I am developing a perl application to be deployed on a production
> > Debian Stable VM. So far, my approach has been to use the debian perl
> > packages (perl modules) and stay within those facilities. I am the
> > sole system operator and wannabe developer, there are no teams of
> > sysadmins or developers.
> >
> > Do you guys who run production debian stable servers use the debian
> > perl packages or use something like PerlBrew? I asked this question on
> > #perl IRC and they answered "PerlBrew/plenv/perl-build" - I want some
> > experienced opinions from the debian community as well.
>
> I do a bit of perl programming (am JONASS on CPAN) and am a Debian
> developer as well.
>
> I use cpanm occationally on my developer laptop, but on production
> servers I only use Debian packages.  I might "cheat" and install
> backported packages or even unofficial .deb packages, but never
> "side-installed" code on production servers.  Reason is that I want a
> single place to keep track of all code installed on the system: APT.
>
> You might consider ask your question at the debian-perl mailinglist, as
> you are more likely to reach Perl folks there, I guess.
>
>
>  - Jonas
>
> --
>  * Jonas Smedegaard - idealist & Internet-arkitekt
>  * Tlf.: +45 40843136  Website: http://dr.jones.dk/
>
>  [x] quote me freely  [ ] ask before reusing  [ ] keep private
>

[toc] | [prev] | [next] | [standalone]

#210557

[Multipart message — attachments visible in raw view] — view raw

On Mon, Jul 01, 2019 at 09:52:18PM +0530, Didar Hossain wrote:
> Hi,
> 
> I am developing a perl application to be deployed on a production Debian Stable
> VM. So far, my approach has been to use the debian perl packages (perl modules) and
> stay within those facilities. I am the sole system operator and wannabe
> developer, there are no teams of sysadmins or developers.
> 
> Do you guys who run production debian stable servers use the debian perl
> packages or use something like PerlBrew? I asked this question on #perl IRC and
> they answered "PerlBrew/plenv/perl-build" - I want some experienced opinions
> from the debian community as well.

I tend to stick to Debian packages as my primary choice, resorting
to off-distribution packages when needed (e.g. not packaged for
Debian, or I /need/ a newer version). Of course it takes some foresight
to guess in advance whether you expect such a situation in the
future.

Rationale: they mesh better with the flow of system updates/upgrades.

I've found Perl packaging in Debian outstanding. The Debian Perl
packaging team does a damn good job indeed.

Cheers
-- tomás

[toc] | [prev] | [next] | [standalone]

#210594

On Mon, Jul 01, 2019 at 06:30:19PM +0200, tomas@tuxteam.de wrote:
> I tend to stick to Debian packages as my primary choice, resorting
> to off-distribution packages when needed (e.g. not packaged for
> Debian, or I /need/ a newer version). Of course it takes some foresight
> to guess in advance whether you expect such a situation in the
> future.
> 
> Rationale: they mesh better with the flow of system updates/upgrades.
> 
> I've found Perl packaging in Debian outstanding. The Debian Perl
> packaging team does a damn good job indeed.

Pretty much the same here.  I was initially hired as a Perl developer,
then gradually moved into more sysadmin duties and, in both roles, I
prefer to stick with the Debian-packaged perl binary.  It gets me
security updates as needed and the only reasons I see a particular need
for PerlBrew and the like are:

1) You need different compile-time options than Debian chooses

2) You need access to a feature that's only present in a newer-than-
   Debian Perl version

3) You want to have the "latest and greatest" for its own sake

Personally, I've never encountered #1 or #2 in practice and if #3
mattered to me, then I wouldn't be running Debian stable in the first
place.

-- 
Dave Sherohman

[toc] | [prev] | [next] | [standalone]

#210596

On 7/2/19 11:20 AM, Dave Sherohman wrote:
> On Mon, Jul 01, 2019 at 06:30:19PM +0200, tomas@tuxteam.de wrote:
>> I tend to stick to Debian packages as my primary choice, resorting
>> to off-distribution packages when needed (e.g. not packaged for
>> Debian, or I /need/ a newer version). Of course it takes some foresight
>> to guess in advance whether you expect such a situation in the
>> future.
>>
>> Rationale: they mesh better with the flow of system updates/upgrades.
>>
>> I've found Perl packaging in Debian outstanding. The Debian Perl
>> packaging team does a damn good job indeed.
> 
> Pretty much the same here.  I was initially hired as a Perl developer,
> then gradually moved into more sysadmin duties and, in both roles, I
> prefer to stick with the Debian-packaged perl binary.  It gets me
> security updates as needed and the only reasons I see a particular need
> for PerlBrew and the like are:
> 
> 1) You need different compile-time options than Debian chooses
> 
> 2) You need access to a feature that's only present in a newer-than-
>    Debian Perl version
> 
> 3) You want to have the "latest and greatest" for its own sake
> 
> Personally, I've never encountered #1 or #2 in practice and if #3
> mattered to me, then I wouldn't be running Debian stable in the first
> place.
> 

+1 here, but in case one need the "latest and greatest" modules, in most
cases it's dead simple to package a not-yet-packaged module with
cpan2deb from dh-make-perl package.

One of the benefits of this approach, is that you don't need to bring
compilers and sources of the dependencies to the production machine.
Build packages on a "development" node and install binary packages on
the production.

In case you need to replicate the setup, or you have more than one
machine one can maintain a repository,making installation of a new
system way easier.

And you also can contribute back to Debian in case you packaged a new
software.

Best,
Alex

[toc] | [prev] | [next] | [standalone]

#210705 — [RESOLVED/Thanks] Re: Debian Perl or Brew Perl for production application?

On Tue, Jul 02, 2019 at 01:36:52PM +0200, Alex Mestiashvili wrote:
> On 7/2/19 11:20 AM, Dave Sherohman wrote:
> > On Mon, Jul 01, 2019 at 06:30:19PM +0200, tomas@tuxteam.de wrote:
> >> I tend to stick to Debian packages as my primary choice, resorting
> >> to off-distribution packages when needed (e.g. not packaged for
> >> Debian, or I /need/ a newer version). Of course it takes some foresight
> >> to guess in advance whether you expect such a situation in the
> >> future.
> >>
> >> Rationale: they mesh better with the flow of system updates/upgrades.
> >>
> >> I've found Perl packaging in Debian outstanding. The Debian Perl
> >> packaging team does a damn good job indeed.
> > 
> > Pretty much the same here.  I was initially hired as a Perl developer,
> > then gradually moved into more sysadmin duties and, in both roles, I
> > prefer to stick with the Debian-packaged perl binary.  It gets me
> > security updates as needed and the only reasons I see a particular need
> > for PerlBrew and the like are:
> > 
> > 1) You need different compile-time options than Debian chooses
> > 
> > 2) You need access to a feature that's only present in a newer-than-
> >    Debian Perl version
> > 
> > 3) You want to have the "latest and greatest" for its own sake
> > 
> > Personally, I've never encountered #1 or #2 in practice and if #3
> > mattered to me, then I wouldn't be running Debian stable in the first
> > place.
> > 
> 
> +1 here, but in case one need the "latest and greatest" modules, in most
> cases it's dead simple to package a not-yet-packaged module with
> cpan2deb from dh-make-perl package.
> 
> One of the benefits of this approach, is that you don't need to bring
> compilers and sources of the dependencies to the production machine.
> Build packages on a "development" node and install binary packages on
> the production.
> 
> In case you need to replicate the setup, or you have more than one
> machine one can maintain a repository,making installation of a new
> system way easier.
> 
> And you also can contribute back to Debian in case you packaged a new
> software.
> 
> Best,
> Alex

Thank you all for your responses. 

My position was indeed to stick with debian packages for the same reasons you
all mentioned. I am simply prone to self-doubt as my background is more of a
systems admin rather than a developer.

Kind regards,
Didar

-- 
Anthony's Law of Force:
	Don't force it; get a larger hammer.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web