Please drop the ^main^ thing Abdulaziz Ghuloum (25 Sep 2009 00:21 UTC)
Re: Please drop the ^main^ thing Derick Eddington (25 Sep 2009 18:23 UTC)
Re: Please drop the ^main^ thing Derick Eddington (25 Sep 2009 19:37 UTC)
Re: Please drop the ^main^ thing Derick Eddington (25 Sep 2009 19:42 UTC)
Re: Please drop the ^main^ thing Derick Eddington (25 Sep 2009 19:40 UTC)
Re: Please drop the ^main^ thing Derick Eddington (25 Sep 2009 19:47 UTC)
Re: Please drop the ^main^ thing Abdulaziz Ghuloum (26 Sep 2009 08:37 UTC)
Re: Please drop the ^main^ thing Shiro Kawai (25 Sep 2009 19:59 UTC)
Re: Please drop the ^main^ thing Andreas Rottmann (25 Sep 2009 20:33 UTC)
Re: Please drop the ^main^ thing Derick Eddington (25 Sep 2009 22:04 UTC)
Re: Please drop the ^main^ thing Derick Eddington (26 Sep 2009 01:16 UTC)
Re: Please drop the ^main^ thing Derick Eddington (25 Sep 2009 21:02 UTC)
Re: Please drop the ^main^ thing Shiro Kawai (25 Sep 2009 22:07 UTC)
Re: Please drop the ^main^ thing Derick Eddington (26 Sep 2009 01:07 UTC)
Re: Please drop the ^main^ thing Shiro Kawai (26 Sep 2009 02:16 UTC)
Re: Please drop the ^main^ thing Abdulaziz Ghuloum (26 Sep 2009 06:10 UTC)
Re: Please drop the ^main^ thing Shiro Kawai (26 Sep 2009 07:59 UTC)
Re: Please drop the ^main^ thing Abdulaziz Ghuloum (26 Sep 2009 08:14 UTC)
Re: Please drop the ^main^ thing Derick Eddington (27 Sep 2009 03:26 UTC)
Re: Please drop the ^main^ thing Shiro Kawai (27 Sep 2009 04:59 UTC)
Re: [OT] English Derick Eddington (27 Sep 2009 05:29 UTC)

Re: Please drop the ^main^ thing Derick Eddington 25 Sep 2009 21:58 UTC

On Fri, 2009-09-25 at 22:33 +0200, Andreas Rottmann wrote:
> Shiro Kawai <xxxxxx@lava.net> writes:
>
> > From: Derick Eddington <xxxxxx@gmail.com>
> > Subject: Re: Please drop the ^main^ thing
> > Date: Fri, 25 Sep 2009 11:23:22 -0700
> >
> >> It's not only for single-component library names.  If you have libraries
> >> (acme foo), (acme foo helper1), and (acme foo helper2), you may want
> >> them all organized under "acme/foo".
> > [...]
> >> A collection of libraries with common prefix (acme ---) might have an
> >> (acme) library and you may want all the libraries organized under
> >> "acme".  I don't know how usual this will be.
> >>
> >> I've been under the impression there's enough demand for the
> >> organize-under-the-same-directory ability of the implicit file name to
> >> justify supporting it.  I could be wrong.  Am I?
> >
> > Just as a data point, I don't have desire to organize a library
> > under a single directory.   I don't mind the library tarball
> > expands into acme/foo.sls, acme/foo/helper1.sls, acme/foo/helper2.sls...
> >
> +1. I do my library collection layouts like this, and don't feel a need
> for the implicit rule, and would rather have it dropped

I also have not been using the current implicit file name support of
different R6RS systems, but that's more a result of their schemes not
being portable and not existing until after I started my collections.
As a result of having many files "littered" outside their logical
collection, I think in my role as a reviewer and manual manager of
collections, I might benefit from it.  On the other hand, the increased
possibilities of where a library's file can be located is a detriment as
a reviewer or manager of collections.

So, I'm conflicted about the implicit file name.  I'll go with whatever
the majority of users of this SRFI want.  So far, that's:

For:
Undecided: Me.
Against: Aziz, Andreas, and Shiro.

Let's allow more time for more people to give their say.  IIRC, I've
heard three other people say they like the implicit file name, and
that's only within the limited range of things I hear.

--
: Derick
----------------------------------------------------------------