Re: Automated package building

2006-01-30 Thread Richard A Downing
On Sun, 29 Jan 2006 18:49:21 -0600 Randy McMurchy [EMAIL PROTECTED] wrote: Please, all, tear it apart and let me know where it needs fixing. I like it. Apart from the personal touches, of course. Does 'Cool, huh?' translate into Russian, Chinese, English? Perhaps 'Impressive, don't you

Re: Automated package building

2006-01-30 Thread Dan McGhee
Bruce Dubbs wrote: Randy McMurchy wrote: I like that. Except I was so tempted to use we in my earlier text, but reworded to avoid it. Would you mind if I did? As long as its not overdone, no. The reader should understand that the 'we' means the collecive editors/authors of the book.

GNOME IDE for Other Programming Tools

2006-01-30 Thread Dan Nicholson
Hi, I while back when I was browsing around Dan Kegel's website (http://www.kegel.com/), I found a page where he advocates for a couple IDEs. Here's the page where he talks about it: http://www.kegel.com/linux/edu/curriculum.html These seems like a prime candidates for the Other Development

Re: GNOME IDE for Other Programming Tools

2006-01-30 Thread Bruce Dubbs
Dan Nicholson wrote: Hi, I while back when I was browsing around Dan Kegel's website (http://www.kegel.com/), I found a page where he advocates for a couple IDEs. Here's the page where he talks about it: http://www.kegel.com/linux/edu/curriculum.html These seems like a prime

Re: Automated package building (LONG)

2006-01-30 Thread Randy McMurchy
Randy McMurchy wrote these words on 01/29/06 18:49 CST: [snip all] Here is an update. Please, if you have a few minutes, check for grammar but really check for technical accuracy. I would appreciate any comments. I feel pretty good about it, and this time I'm finished, but much has been added

Re: Automated package building (LONG)

2006-01-30 Thread Bruce Dubbs
Randy McMurchy wrote: Automated Building Procedures (sect2 header) There are times when automating the building of a package can come in handy. Everyone has their own reasons for wanting to automate building, and

Re: Automated package building (LONG)

2006-01-30 Thread Randy McMurchy
Bruce Dubbs wrote these words on 01/30/06 16:15 CST: [snip all] Thanks for the pointers, Bruce. You obviously read it very carefully, and really didn't expose anything other than some semantical changes. I committed it earlier, but will go back and fix the things you pointed out. I especially

Re: Automated package building (LONG)

2006-01-30 Thread Randy McMurchy
Bruce Dubbs wrote these words on 01/30/06 16:15 CST: chmod 755 blfsyestest1 blfs-yes-test1 (readability) Boy, I bet you *hate* the KDE program names. Notice that when they *do* manage to split the names up a tad for readability, they use underscores instead of hyphens, which I know

Re: Automated package building (LONG)

2006-01-30 Thread Bruce Dubbs
Randy McMurchy wrote: Bruce Dubbs wrote these words on 01/30/06 16:15 CST: chmod 755 blfsyestest1 blfs-yes-test1 (readability) Boy, I bet you *hate* the KDE program names. Notice that when they *do* manage to split the names up a tad for readability, they use underscores

Re: GNOME IDE for Other Programming Tools

2006-01-30 Thread Jeremy Huntwork
Dan Nicholson wrote: P.S. I'm loving the wiki! I've got a few ideas I'd like to add when Trac hasn't gotten fully integrated. Ideas for the wiki or ideas for BLFS? Whenever we go live with Trac, I believe we can just drop our current installation in place (minus the tickets which will need

Re: GNOME IDE for Other Programming Tools

2006-01-30 Thread Dan Nicholson
On 1/30/06, Jeremy Huntwork [EMAIL PROTECTED] wrote: Ideas for the wiki or ideas for BLFS? Whenever we go live with Trac, I believe we can just drop our current installation in place (minus the tickets which will need to be regenerated). So, if you're holding off from adding to BLFS's wiki

trac Implementation

2006-01-30 Thread Bruce Dubbs
We have had a trac beta up now for a couple of weeks. The time has now come to implement it. The plan is to use it as a substitute for Bugzilla and ViewCVS as well as to implement the wiki. The main web site will remain unchanged. To do this, we will need to disable adding new bugs and