On 2010-03-16, at 21:32, Groepaz wrote: >>> So if anybody offers these modules for download, creating a >>> replacement >>> library is really easy. >> >> Now - for it to make it to mainstream, instead of patches to the >> original read/write or anything - can't we simply have those two >> files >> in the source tree and add the three commands above to the build >> process? Even conditionally or so? > > to me it sounds like a better idea to maintain such files in a > seperated > sourcetree ... or the libsrc will quickly turn into a giant mess > full of very > specific replacement files :) i could probably build about 20 > different libs > from what i used in the past couple of years =P I see your point. Of course I wouldn't like the "giant mess" either. What I was thinking, was rather like "support for additional, important hardware". Where "important" is the keyword. It's a bit like with the Linux kernel - if it is supposed to support additional hardware - the source tree has to grow. Sure - most gfx cards f.e. can be driven with 16col vga driver, right? But native support for new hardware capabilities is being constantly added. There is no escape from that. The trick is to keep it maintainable. Thus the maintainer has the ultimate word on what goes into libsrc, and what not. To me IDE64 would qualify as "important" hardware that would benefit a lot from this sort of support. Like with DTV64 - even if to me DTV is far from being as "important" as IDE64, I would still admit this is hardware worth supporting - similarly to what e.g. viceteam apparently thinks. Thus it IMHO depends on how we look at it. If we look at it as a "new support for important hardware", which can be achieved with virtually no development cost - I'd find it quite tempting. Whether JiffyDOS, DTV64 or anything else would fall into the same category - that's of course up to the libsrc maintainer. The same goes with IDE of course ;-) Regards, -- SD! ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.Received on Wed Mar 17 18:41:30 2010
This archive was generated by hypermail 2.1.8 : 2010-03-17 18:41:33 CET