| 1 |
Richard Freeman wrote: |
| 2 |
> I still don't see why we need to be encoding metadata in filenames. PERL |
| 3 |
> doesn't care what a file extension is, python doesn't care, bzip2 |
| 4 |
> doesn't care, tar doesn't care, gzip doesn't care, and even ld-linux.so |
| 5 |
> doesn't care. I'm sure that in at least some of these cases they end up |
| 6 |
> parsing parts of the file twice - once to figure out what it is, and the |
| 7 |
> second time to actually handle it. I'm actually hard pressed to think |
| 8 |
> of any unix-based software that uses the filename to store a mandatory |
| 9 |
> file format versioning specifier of some kind. |
| 10 |
|
| 11 |
I have to admit I'm in the same camp with Richard, and don't understand |
| 12 |
the necessity. I'm also opposed to creating arbitrary suffixes to the |
| 13 |
ebuild extension, for cosmetic and compatibility reasons. |
| 14 |
|
| 15 |
Plus, I don't really grasp the whole "we have to source the whole ebuild |
| 16 |
to know the EAPI version" argument. It's one variable, in one line. |
| 17 |
Can't a simple parser get that and go from there? |
| 18 |
|
| 19 |
Steve |
Archives