[binarycloud-dev] list of make issues

[alex b. <en...@tu...>]

If I am correct, here's the list of issues:

    -we need to be able to deal with multiple "named" user directories that
use the same binarycloud/ package tree. (I 100% agree, this will be done)

    -Justin would like to see the package delimiter in import statements
change from . to something else that no one would ever think of using in a
filename: : or :: or # or whatever.
I am not really opposed to changing binarycloud.core.Perm to
binarycloud:core:Perm, actualy - though I would like Odysseas' opinion on
that one.

    -Justin would also like to have the ability to name his files with
whatever extensions he likes. However, I just thought of something:

    Justin, are you only interested in having that ability within the tmpl/
directory in user?. We have to establish a standard for entity naming,
because they will be interpreted by the make system and moved around at
build time, for example - but we may be able to just "assume" that
everything under tmpl will be a template, and thus only need language
keying.

Putting the above aside, the only way I see to allow for developer-defined
extensions is to create a file with extension -> type mappings that make
uses to determine file type at build time.

for example:

".master" = 'php'
".layout" = 'php'
".phtml" = 'php'

etc.

Again, I don't necessarily object to that, but Odysseas is the make expert
among us, and I would like his opinion.

--------

If I missed anything, let me know.

_alex