[pkg-bioc] CVS %p

Dirk Eddelbuettel edd at debian.org
Thu May 24 16:22:20 UTC 2007


On 24 May 2007 at 17:08, Steffen Moeller wrote:
| Hi Dirk,
| 
|  I played with the title and have then forgotten about it ... sorry for that. 
| The figure I did against your pledge in CVS since I needed to see what I was 
| doing. Should I have changed something else ... well ... so I probably have, 
| it was not intended to be perceived as some sneeky backdoor business.
| 
| The diff to my printout from this morning:

Ok, changed my mind. Let me take them one by one:
 
| * s/really suggests/obviously fosters/

No, that's "Genglish". 

| * The whole para "At this point, CRAN and BioConductor ...." I strongly 
| suggest to merge with the description of R two paras above.

I'd prefer not.

| * s/is orders of magnitude/is considerably/

'Orders of mag' is stronger, and that is the point am trying to make here.

| * s/data base/database/

Yes, score is now 5 database to 0 data base. Caught the last one. 

| * First para of "Technologh and Approach": s/functionality we 
| added/functionality added/

No. Gotta list our contribution somewhere/

| * The enumeration below should start with capitals at each item

Ok, done.

| * just below: s/package \(that do/packages (that do/

Yes, thanks.

| * s/where needed, // and on the same line s/Depends/dependencies/

Ok, left 'where needed' to show that this does not apply to all, changed to
dependencies . 

| * The para right below starting with "This main step may fail" I suggest to 
| rephrase as: "The database is steadily augmented as new packages

augment is not a verb you can use on database. But I fixed the double 'may'
in the 1st sentence.

| are introduced to the build process. Consequently, with packages
| from separately treated repositories, inter-package dependencies may
| not all be resolved when first starting the script." And maybe this bit should 
| go elsewhere.

I did not at this

| * s/at the end//

Ok.

| * s/\(not.yet.announced\)/shared/

Nope.

| * It should be either current state or {\em status quo}, I'd say, not both 
| merged.

Ok. I also shortened the section title to 'Open Issues '

| * Section "Status Quo and Open Issues", 2nd para, 2nd and 3rd 
| sentence: "However, as of mid-May ... announced. The project would .... 
| backup host" should be deleted.

No, why?  We DO need a host.

| * Following sentence: s/force these 1700/force all 1700/

Ok, thanks

| * s/However, it/It/

Didn;t find that.

| * s/One obvious case is where packages require external libraries/Obviously, 
| packages are difficult to handle that require external libraries./

No, left as is

| * s/for each individual builds/for each individual build/

That had been fixed already, thanks.

| * Please fix the line below that one with the unfortunate "(Intel) x86 and 
| (AMD) amd64" mixup of Debian platforms and vendor names.

ok

| * s/For the Debian packages/For Debian packages/

Better as is, I think

| * s/generated\) ./generated)./

Had been fixed it seems.

| * s/separate folder of the publicly accessible folder on the CVS tree/separate 
| folder of the publicly accessible CVS tree/

Good one, I made it 'separate directory of ... tree' Only looser operating
system have folders :)

| * Consider to remove the para "Information reuse" (low priority on my side)

Happens to be important to me, sorry

| * s/of the CRAN network runs/of the CRAN network run/

Had been fixed, thanks.

Current tex and pdf attached. Will also checked in in a second.

Dirk

-- 
Hell, there are no rules here - we're trying to accomplish something. 
                                                  -- Thomas A. Edison



More information about the pkg-bioc-devel mailing list