Hi all,
I re-ordered the quotes to avoid sending multiple replies but answer in order.
> 2015-05-04 16:34 GMT+02:00 Jens Rehsack :
> Hi,
>
> initially planned being one big topic for my QAH attendance, but Murphy
> decided to keep me busy otherwise (broken car, for everyone who didn't
> recogniz
On 6 May 2015 at 12:33, breno wrote:
> That said, I would rather see it in a new module than have it in
> File::ShareDir itself. Kinda like how nowadays I prefer Path::Tiny over
> File::Spec + Cwd (or even Path::Class).
There is still a need for a simple mechanism for hooking FSD from a 3rd
par
Hi Jens!
I'd love to have a module providing an improved and modern interface to
File::ShareDir and I think the entire community would greatly benefit from
it - not just the toolchain. That said, I would rather see it in a new
module than have it in File::ShareDir itself. Kinda like how nowadays I
I am not opposed in principle to redesigning File::ShareDir, but I want to
be *very* clear about the proposed design changes, impact on various parts
of the toolchain, and back-compatibility concerns before anything moves
beyond the design phase. This code sits at the very heart of the cpan,
called
Hi,
Is it really necessary to introduce those new features (bloat?) in the
existing File::ShareDir ?
Why not just fork and keep the original File::ShareDir light?
What problems would be solved if the new features you plan were added to
the existing File::ShareDir? Which existing application would
Hi,
initially planned being one big topic for my QAH attendance, but Murphy
decided to keep me busy otherwise (broken car, for everyone who didn't
recognize on QAH...).
Well - things are settling meanwhile and I have a few moments to think
about the tasks I missed to finish in Berlin. One is File
6 matches
Mail list logo
