Contents of directories named Packages or packages ignored by GitHub in calculating language statistics

[dalehenrich]

If one uses a directory named Packages or packages for their Cypress packages, GitHub will skip over those directories when looking for Smalltalk files.

The workaround is to use another name like repository. Cypress will work fine and GitHub will find your .st files for calculating language statistics.

[dalehenrich]

Note that we should rename the directories in the reference implementation so that the language stats will reflect things correctly

[janvrany]

On 03/04/13 19:45, Dale Henrichs wrote:

Note that we should rename the directories in the reference
implementation so that the language stats will reflect things correctly

What name do you suggest?

—
Reply to this email directly or view it on GitHub
#16 (comment)
Bug from
https://github.com/notifications/beacon/BTeKxI_0bFOw-XPWQyOrf53uwLhAduJ0ydR7G_ORcccfbAKNeprZcqidQAE9fhrL.gif

[dalehenrich]

I guess my response didn't make it to the list ...

Jan,

There isn't a good alternative ... I'm falling back to the name that I originally used: `repository`, but `packages` is really the best name ... Anyone else have a suggestion?

Dale

[mkobetic]

The specification doesn't require use of a 'packages' or 'repository' directory, so this is more of an issue with the reference implementations, not with the spec, correct?

[dalehenrich]

Exactly right ... I had also been recommending that the directory be called packages ... so I'm making a little bit of noise:)

Dale

----- Original Message -----
| From: "Martin Kobetic" notifications@github.com
| To: "CampSmalltalk/Cypress" Cypress@noreply.github.com
| Cc: "Dale Henrichs" dhenrich@vmware.com
| Sent: Sunday, April 7, 2013 3:11:30 PM
| Subject: Re: [Cypress] Contents of directories named Packages or packages ignored by GitHub in calculating
| language statistics (#16)
|
| The specification doesn't require use of a 'packages' or 'repository'
| directory, so this is more of an issue with the reference implementations,
| not with the spec, correct?
|
| ---
| Reply to this email directly or view it on GitHub:
| #16 (comment)
|