On 05/02/2012 11:32 AM, Bruce Dubbs wrote: > > I can see both sides of the discussion here. If someone works on a section of > the book for quite a while, I think it's natural to develop a sense of > 'ownership' of that work. I don't think anyone would object if another comes > in > and corrects a misspelling or md5sum or somthing like that. We should be able > to touch up each other's work, but things that would appear to be style are > not > quite so simple. And sometimes that "ownership" sticks for a long time! ;-)
> The easy way out is to ask in advance and offer to make the > change. The key is trying to avoid surprises. I agree in principal, but I'll go on record and say that if anybody wants to do something with packages that are historically "mine"....please speak up and then get to work! I'm thankful that Andy and Fernando teamed up to do LibreOffice. I hate that the book can suffer in any way just because I can't dedicate the time I'd like to. For instance, right now, the previously mentioned OpenJDK changes are probably a month out yet. I wouldn't be the least bit hurt if somebody else wanted to do it faster. I'd certainly appreciate consulting, but it is not necessary. Same thing for Xorg. 7.7 should be out very soon, and I think it could definitely benefit from some style other than that outdated layout I added several years ago. One suggestion, for instance, is to separate out the parts only used for testing the X server (twm, xinit, mesa demos). These aren't part of the "katamari" nor is Xp which was required for Java. Another, if done correctly, the packages could even be separated out instead of arbitrarily assigning a build number to it (the -2 in 7.6-2). Even though I've recently argued against it, there is some merit to separating the xorg packages. Now, I will continue to argue against adding 200+ pages to the book, but having thought about it a little more, something with the organization of the Python modules page for each section might make a nice compromise. I suggest that we still use the wget and md5 files and a loop, but also provide descriptions and dependencies on the page. I don't have the time or desire to do that, but as it is right now, there is absolutely no documentation on what might or might not be needed. I suspect that many of us just build the whole enchilada, which completely negates the point of separating the packages in the first place. We might as well just write a Makefile with a "World" target. The fonts are another thing. We probably need only the font-util package and an assortment of TTF fonts now that the legacy packages are gone. -- DJ Lucas -- This message has been scanned for viruses and dangerous content, and is believed to be clean. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
