On Mon, 25 Jun 2007 20:30:36 +0200, Juerd Waalboer wrote:
A useful, easily installable library bundle does not have to be in the
core distribution.
Debian already has its own split between perl and perl-modules. This is
a great scheme that allows Debian to use Perl in the base system,
On Mon, 25 Jun 2007 09:57:18 +0200, Hakim Cassimally wrote:
On 23/06/07, chromatic [EMAIL PROTECTED] wrote:
On Friday 22 June 2007 11:07:35 Chas Owens wrote:
Please, god, no. Or at least make two distributions: Bare Perl 6 and
Perl 6. Many companies have a Only Core Perl policy. They refuse
On 6/25/07, Peter Scott [EMAIL PROTECTED] wrote:
I will just voice my support for putting best-of-breed modules for very
common tasks (CGI, DBI for sure) in the core.
Of course, then you get the disadvantage that most users will see new
versions of those modules as often (or seldom, as it
How about a Bundle::Common?
Streamline both the core and the inclusion of the most commonly used
modules? The core does include the CPAN module, right?
Personally, I *prefer* grabbing what I need piecemeal, but I understand
making it easy if possible
--- Luke Palmer [EMAIL PROTECTED] wrote:
Hakim Cassimally skribis 2007-06-25 9:57 (+0200):
Releasing a language without a useful, easily installable library bundle
could quite reasonably be construed as a stupid business practice.
A useful, easily installable library bundle does not have to be in the
core distribution.
Debian
On Monday 25 June 2007 00:57:18 Hakim Cassimally wrote:
Releasing a language without a useful, easily installable library bundle
could quite reasonably be construed as a stupid business practice.
Of course. Yet some dozen years later, the argument for keeping interfaces
such as File::Find
Getting back to the Web Module,
the following could help a lot
if there were in the core or as a 'core' downloadable bundle :
- DBI
- ORM system
- Caching system
- Sessions (server side cookies)
- XML parser
- JSON parser
I guess that it will be fair enough for actual web apps.
templating
Juerd Waalboer writes:
Smylers skribis 2007-06-21 23:23 (+0100):
Of course. But there's a big difference between the attitude of
'let's do the best we can right now' and 'this is our one chance to
do this right'.
I think that for some things, mainly for setting community standards
On Thursday 21 June 2007 15:23:38 Smylers wrote:
Has Larry yet decreed whether Web will be bundled with Perl 6?
I also like to proceed from the assumption that the only core modules should
be those required to install other modules.
-- c
On 6/22/07, chromatic [EMAIL PROTECTED] wrote:
On Thursday 21 June 2007 15:23:38 Smylers wrote:
Has Larry yet decreed whether Web will be bundled with Perl 6?
I also like to proceed from the assumption that the only core modules should
be those required to install other modules.
-- c
On Fri, Jun 22, 2007 at 02:07:35PM -0400, Chas Owens wrote:
On 6/22/07, chromatic [EMAIL PROTECTED] wrote:
I also like to proceed from the assumption that the only core modules
should be those required to install other modules.
Please, god, no. Or at least make two distributions: Bare Perl
On 6/22/07, Chas Owens [EMAIL PROTECTED] wrote:
Most of the time the policy is enacted by lower-case-l lazy sysadmins
who can't be bothered to type
perl -MCPAN -e install Foo::Bar
My normal route around them is to install the module into the home
directory of the user who is going to run the
On 6/22/07, jerry gay [EMAIL PROTECTED] wrote:
On 6/22/07, Chas Owens [EMAIL PROTECTED] wrote:
Most of the time the policy is enacted by lower-case-l lazy sysadmins
who can't be bothered to type
perl -MCPAN -e install Foo::Bar
My normal route around them is to install the module into the
On Friday 22 June 2007 11:07:35 Chas Owens wrote:
Please, god, no. Or at least make two distributions: Bare Perl 6 and
Perl 6. Many companies have a Only Core Perl policy. They refuse
to install CPAN modules because We don't trust them.
I think of this the same way I think of Do not drink
On 6/22/07, chromatic [EMAIL PROTECTED] wrote:
On Friday 22 June 2007 11:07:35 Chas Owens wrote:
Please, god, no. Or at least make two distributions: Bare Perl 6 and
Perl 6. Many companies have a Only Core Perl policy. They refuse
to install CPAN modules because We don't trust them.
I think
The fact that you'll be able to do that in Perl6 excites me. One of the
things I use with the existing Perl5 unfortunately at times, is
commercial software which compiles Perl code into various Microsoft
formats: services, system tray icons, dll's and executables.
That proved to be extremely
Moritz Lenz writes:
You could help by contributing some suggestions to what the new Web
module should be able to do, and how so. Web is hopefully CGI done
right, and still in its early planning stage.
Web module? This is the first I've heard of it. Where is it being
planned, if not on this
Darren Duncan writes:
At 6:37 PM +0100 6/21/07, Smylers wrote:
Web module? This is the first I've heard of it. Where is it being
planned, if not on this list?
It was being discussed on the perl6-users list, last year.
Thanks.
Smylers
Smylers wrote:
Moritz Lenz writes:
You could help by contributing some suggestions to what the new Web
module should be able to do, and how so. Web is hopefully CGI done
right, and still in its early planning stage.
Web module? This is the first I've heard of it. Where is it being
Moritz Lenz writes:
Smylers wrote:
Moritz Lenz writes:
Web is hopefully CGI done right
... why are we hoping that it will be done right?
Because we hope we learned from the past. There are several other
modules that fullfill most of CGI's tasks, some of them do most of it
20 matches
Mail list logo
