Re: renaming libcruft

[Mike Miller]

On Tue, Aug 14, 2012 at 6:19 PM, Rik wrote:
> On 08/14/2012 01:11 PM, Mike Miller wrote:
>> Rik also wrote:
>>>> I see it being more of a problem where the directory names
>>>> are not descriptive of what is inside.  For example, libcruft gives me no
>>>> indication of what I should really expect to find there.  When John gets
>>>> back in a few days I'd like to see about renaming that directory.  It is a
>>>> bunch of old Fortran code so maybe "liboctfort", "libfort", etc.
>> I do like this idea, and I'd want to see something that indicates the
>> library belongs to Octave. On Debian, libcruft is installed alongside
>> all other system libraries, so it might be good to namespace it like
>> liboctfort or liboctf77, or even liboctcruft :)
>>
> I also like this idea.  We already make liboctinterp for the interpreter
> and liboctgui for the GUI so putting libcruft into the liboct naming space
> makes sense.
>
> What other suggestions do people have for this directory?  Current list is
> small
> liboctfort
> liboctf77

Ok, no one else has responded, I'll throw out a few more in no
particular order, just to add to the pool.

liboctfortran
liboctinternal
liboctlowlevel
liboctugly
liboctmisc
liboctclutter

-- 
mike