On Thu, May 21, 2009 at 02:18:54PM -0700, Marek Szuba wrote: -> The two files have been added to the top-level directory, as I am not -> sure at this point whether we should actually have them merged into the -> master. Ebuilds do not really belong to packages they describe, the -> ultimate goal of creating such a file is to have it included in a -> Portage repository (preferably the primary, Gentoo-maintained one - -> which unfortunately depends on whether any maintainers are interested -> in maintaining it. Then again, Biopython is in there so we've got a -> chance.). Not to mention that one needs to get the ebuild first and -> the package afterwards. From this point of view, it may make more sense -> to have them posted on Google Code. On the other hand, keeping them in -> Git may help us keep them up to date... Last but not least, if we do -> keep them in Git there is the question of the name of the directory to -> hold them - in case of C packages this kind of stuff (Debian -> package rules, RPM .spec files, ebuilds etc.) go into the 'dist' -> directory, which however in case of Python conflicts with distutils. -> 'linux' on the other hand may be too specific, as Portage also works -> under FreeBSD. 'misc'?
Maybe 'misc', or 'conf', or 'ext'? --titus -- C. Titus Brown, c...@msu.edu --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pygr-dev" group. To post to this group, send email to pygr-dev@googlegroups.com To unsubscribe from this group, send email to pygr-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/pygr-dev?hl=en -~----------~----~----~----~------~----~------~--~---
