Why do you create a separate .ebuild for each version of a given package? It would be nice to have a single .ebuild, and a way to have separate routines for distinct versions of the software, since the steps needed to build and install a program don't frequently change. Reproducible: Always Steps to Reproduce:
this came up before and the answer is because it's easier to manage some issues with a 1 file format: CVS mismatches are more likely to happen file becomes unmanagable for packages that change greatly with patches between versions (there are some)
The purpose of CVS is to handle conflicts (mismatches)! I know there are some packages with big changes between versions, but most of the time, you just copy the old .ebuild to create the new one for the software's new version, don't you? This makes CVS unnecessary, beacause there are only 1 or 2 revisions of an .ebuild this way; not like if you have made the changes to the original .ebuild.
regardless of how you may feel, the discussion ended with a 'no' if you feel differently, please open it up on the mailing list gentoo-dev
Sorry, I abhor mailing lists :-( I never used one.. Can you please ask about this issue on the mailing list to see if there's anyone who agrees with me? Maybe a poll in the forum?
--Hope this bug won't get deleted for a while--
If you want sth better ask yourself, we usually don't play messengers.
sorry, i understood now. it really better to have separate .ebuilds.. Gentoo seems to have a consistent philosophy of having separate files for everything which is not a bad thing
no problem ... sometimes what seems like a really cool idea may not be so ;)
(i dont abhor mailing lists btw... i like them 8-/ )
