Re: NEW: books/svn-book
Mike Pechkin <[EMAIL PROTECTED]> wrote: > Just for fun: > 1. I don't understand LICENCE of the book The summary makes it look like a two-clause BSD license. The actual text has a lot of verbiage... the most offensive thing I see is that you may not distribute the book under some copy-protected/DRM scheme. PERMIT_*=Yes. > 2. NO pkg/DESCR Oh, come on. Version Control with Subversion describes Subversion, a new version control system designed to supplant CVS. There you are. If a book is available in multiple formats, as this one is, which one do we package? -- Christian "naddy" Weisgerber [EMAIL PROTECTED]
Re: NEW: books/svn-book
If a book is available in multiple formats, as this one is, which one do we package? PDF or HTML would be my first choices. If those were the only choices, I'd say do both.
Re: NEW: books/svn-book
On Wed, Aug 03, 2005 at 08:57:36AM -0400, Ian Darwin wrote: > > > > >If a book is available in multiple formats, as this one is, which > >one do we package? > > > > > > > PDF or HTML would be my first choices. If those were the only choices, > I'd say do both. HTML would be my number one choice, since it can be viewed nicely without X11 with lynx, which is in the base system. -- steven
Re: NEW: books/svn-book
HTML would be my number one choice, since it can be viewed nicely without X11 with lynx, which is in the base system. Yes, and therefore plain text should be #1 because /bin/cat was in V7 unix. :-) If I'm reading a book online, however, I hope to be able to see it in a form that is close to the real thing, the physical book. So I vote for PDF to be #1. Enough of "My format's better than your format" :-) Now back to work.
