On Friday, December 31, 2010 11:16:41 Enrico Weigelt wrote: > * Mike Frysinger schrieb: > > On Thursday, December 30, 2010 01:46:34 Enrico Weigelt wrote: > > > Little example, where I'm working on right now: coreutils and gnulib. > > > Imagine, these jerks not just collected hundreds of (sometimes really > > > broken) tests and workarounds instead of fixing the source - they > > > also collected them in another "package" called gnulib, which gets > > > fetched via git (from the current head instead of some release tag!) > > > and _copied_ into the coreutils source tree by some obscure > > > "bootstrap" script. Wow, self-modifying code. Violating all rules > > > of the very first semester in software engineering ;-o > > > > yeah, once you start fixing Microsoft's runtime library and Solaris' C > > library and old UNIX systems whose owners long died and ........, feel > > free to get gnulib obsoleted. but until that happens, stop living in an > > unrealistic world. gnulib exists for a very real reason and is > > extremely useful to many many people. > > You didn't get my point. I was talking about the way of copying > in (parts of) gnulib into other package's source tree in an > unpredicable way, directly within the build process. i'm guessing you've never actually used gnulib and thus know little about how it works. importation of it isnt "unpredictable" at all. the developer doing the import closely controls what functions exactly they wish to import. > The clean way (tm) would be making it a real library again, clearly you dont follow anything about gnulib. they're already working on an actual shared library now called libposix. > I'm currently in the process of doing exactly that. i'm sure that will totally see real use and isnt a complete waste of time -mike