Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rename nss_cache directory to nsscache #4

Closed
jaqx0r opened this issue Mar 14, 2015 · 3 comments
Closed

Rename nss_cache directory to nsscache #4

jaqx0r opened this issue Mar 14, 2015 · 3 comments

Comments

@jaqx0r
Copy link
Contributor

jaqx0r commented Mar 14, 2015

Original issue 3 created by jaqx0r on 2008-01-25T21:21:39.000Z:

Hi again,

The program is called nsscache, but the modules install under nss_cache.
This is inconsistent, and makes packagin harder.

@jaqx0r
Copy link
Contributor Author

jaqx0r commented Mar 14, 2015

Comment #1 originally posted by jaqx0r on 2008-02-04T05:09:47.000Z:

I disagree.

The library name is nss_cache, and the executable name is nsscache. The
"inconsistency" only exists if you think that they are one and the same.

Other applications can reuse this code with "import nss_cache" in their source.

Can you cite examples of how this makes packaging harder?

@jaqx0r
Copy link
Contributor Author

jaqx0r commented Mar 14, 2015

Comment #2 originally posted by jaqx0r on 2008-02-04T07:37:31.000Z:

Hi,

It's not that it's much harder to package, but I expected "import nsscache" to work.
I'm packinging it up for Fedora, and it took me a while to find out why my rpm didn't include all the files in
the python site-packages dir. Until I added the underscore :-)

Not a major issue, just cosmetic.

@jaqx0r
Copy link
Contributor Author

jaqx0r commented Mar 14, 2015

Comment #3 originally posted by jaqx0r on 2008-02-08T03:33:10.000Z:

Exciting news about the Fedora packaging! Thanks!

@jaqx0r jaqx0r closed this as completed Mar 14, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant