As one of those 'users' (an AT actually), I would find having the eapi in the filename quite annoying - especially having several ebuilds in the tree that differ _only_ in their eapi number (and doing different things). It just Seems Wrong - nearly all binary files do versioning/format information inside the files, and one of the main things I like in unix is that file format is *independant* of what you actually name it (a text file can be named *.wibble, or even have no extension at all and nothing will break). Filenames are generally quite mutable - changing the filename is just a single 'mv', whereas if you need to edit the file to change the type that generally requires more effort, you need to think more about what you're doing, and so theres less chance to break stuff (a eapi-1 file accidentally gets moved to eapi-2, lots of stuff breaks, whereas if its in the file you notice you need to edit it to actually make it eapi-2 compliant)
And please, please, don't base the decision on who can shout loudest or longest. Think through each option (filename, inside file, metadata, Manifest, directories, seperate db, ...) logically, weigh the pros and cons, and decide on the one that would best fit gentoo on technical grounds, not just on the one backed by the most vocal people. If you make the wrong decision it could seriously screw gentoo over and make it very painful in the future -- [EMAIL PROTECTED] mailing list
