Subdirectory name of source code
Opened this issue · 3 comments
GoogleCodeExporter commented
It would be better if the source code were into a directory with a name ready
to import.
So, instead of:
import l4g "log4go.googlecode.com/svn/stable"
we could use it directly from:
import "log4go.googlecode.com/svn/l4g"
Original issue reported on code.google.com by raul....@sent.com
on 3 Jul 2010 at 8:58
GoogleCodeExporter commented
The import statement actually uses the package name by default, not the last
name in the directory path. So, if you don't rename it l4g, it's log4go. For
the purposes of code brevity, I like to use l4g, but I submit that log4go
should still be the package name.
Original comment by ethereal...@gmail.com
on 4 Jul 2010 at 4:14
- Added labels: Priority-Low, Type-Other
- Removed labels: Priority-Medium, Type-Defect
GoogleCodeExporter commented
I've been confused with that. Anyway if it's used the same name for both
directory and package (like in Go core) then people will know how is called the
package
import "log4go.googlecode.com/svn/log4go"
Original comment by raul....@sent.com
on 4 Jul 2010 at 4:59
GoogleCodeExporter commented
The argument that I have heard is that the subdomain matching the package name
is just as verbose, and gives you the option to have /svn/stable, /svn/trunk,
etc with little effort.
Original comment by ethereal...@gmail.com
on 5 Jul 2010 at 10:42