there would be a set of work to do on the manager it's self, which would be tricky but not soo bad, then there would be maintainer cooperation, which I wouldn't be part of, i have no interest in maintining and testing every single variant of everyone of my pkgs. We are a small team of maintainers with lots to maintain already, and I wouldn't like none much having others mess with my patch files to get other variants work while breaking mine and me not knowing about it. I think the layout and idea is good but the implementation of it lacks, welll pezzaz. Like for all the extra work what does the maintainer get out of it other then more work?
[EMAIL PROTECTED] writes: >Sounds great vasi...we could have new fields such as VarientConflicts >ot FlavorDepends to take care of dependancies like that, but it is a >whole lot of work...what are your suggestions for starting, so we can >implement it piece by piece? -=[JFH] Justin F. Hallett <Systems Analyst> -=[JFH] Rendek Communications Inc. -=[JFH] [EMAIL PROTECTED] ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
