--- On Mon, 4/1/10, Eric Wilhelm enoba...@gmail.com wrote:
From: Eric Wilhelm enoba...@gmail.com
If Parrot itself supports trans-language calls (which
I'm led to
understand it can?) then a single index gives us the
potentially huge
win of cross-language dependencies.
Does it? Tell me
# from Zefram
# on Monday 04 January 2010 03:23:
use perl5:Text::Wrap 'wrap';
That would seem to settle it, then: perl5:Config::INI does not
conflict with perl6:Config::INI.
I believe that's supposed to be use Text::Wrap:fromperl5. But yes
it's a different set of namespaces.
--Eric
--
(I had a big response going to various details of this thread, and then
realized that from Plumage's perspective, the details don't actually
matter much; see the more general email below.)
On Mon, 2010-01-04 at 10:45 -0500, Jesse Vincent wrote:
This brings us to How do we get there from here?
It's been something of a long-standing (second-order) problem that
packages are just tarballs (or bzipball, or zips, etc).
The lack of a standard file extension means that we can't sanely
implement features like double-click to install on operating systems
and browsers with file extension
I'd rather like to avoid adding additional complexity to the current
index files.
Instead, what about switching to a native SQLite index for the new system.
This is working quite nicely in the JSAN now, and it greatly
simplifies things because you can download the index much more simply.
1.
# from Adam Kennedy
# on Monday 04 January 2010 16:07:
I'd rather like to avoid adding additional complexity to the current
index files.
...
This would, of course, mean that SQLite and DBI support is needed in
... the modules needed to install other modules ...
^
On Mon, Jan 4, 2010 at 5:15 PM, brian d foy brian.d@gmail.com wrote:
02packages is actually quite flexible. There's a line in the header
that tells consumers what the columns are. Since we've used the same
three columns, a lot of stuff has assumed that the order and meaning
will always be
7 matches
Mail list logo
