Question about autogenerated data files

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello all, eric (a Python IDE which is built around QScintilla) supports code completion and tool tips. For that feature to work, it needs API files which can be autogenerated by some scripts from upstream (one for the Python builtins & modules, the o

Re: A couple of questions

In case Justin's mail didn't answer all your questions... Shachar Shemesh <[EMAIL PROTECTED]> wrote: > Well, you would need a helper program to actually change it, as the > password is encrypted. Otherwise, yes it's a configuration file. Well, the line is a bit blurry here, I admit. Note that pa

Re: Question about autogenerated data files

Torsten Marek said: > eric (a Python IDE which is built around QScintilla) supports code > completion and tool tips. For that feature to work, it needs API files > which can be autogenerated by some scripts from upstream (one for the > Python builtins & modules, the other one for PyQt APIs). > > I

Re: Question about autogenerated data files

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Matthew Palmer schrieb: > Torsten Marek said: > >>eric (a Python IDE which is built around QScintilla) supports code >>completion and tool tips. For that feature to work, it needs API files >>which can be autogenerated by some scripts from upstream (o

Re: A couple of questions

Florent Rougon wrote: In case Justin's mail didn't answer all your questions... It did. Shachar Shemesh <[EMAIL PROTECTED]> wrote: Well, you would need a helper program to actually change it, as the password is encrypted. Otherwise, yes it's a configuration file. Well, the line is a bit

Re: A couple of questions

Shachar Shemesh <[EMAIL PROTECTED]> wrote: > After your explanation, the only thing I still have doubts over is > whether the files should not go into /var/cache instead. Erm, which files? -- Florent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Cont

[may be a bit OT] How to point upstream authors in the right direction

Yo! I just stumbled upon a very interesting article about what upstream software authors can do to make the packager's life easier: This is exactly the same thing I have tried to start on the Debian Wiki at:

Re: A couple of questions

Florent Rougon wrote: Shachar Shemesh <[EMAIL PROTECTED]> wrote: After your explanation, the only thing I still have doubts over is whether the files should not go into /var/cache instead. Erm, which files? During the process files are encrypted. Their key is stored under /var/lib/name,

Re: A couple of questions

> That's not a problem. The initial password is an empty file. Since > it has a different owner and non-standard permissions it's a bit of > a headache to create and remove properly in post{inst,rm}, but no > big deal. Just to be clear, there should be no non-conffile configuration file shipped in

how to handle bugs (wishlist) in packages we build depend on

Hello, Here is the situation: We have #290338 against ara [1]. Also we believe we have done our packaging right, but as you can see from the buildd logs [2] of the latest version, we end up with: -log- dpkg-genchanges: arch-specific upload - not including arch-independent packages d

Re: A couple of questions

Shachar Shemesh <[EMAIL PROTECTED]> wrote: > The slight dilemma is whether /var/cache or /var/spool would be a > better choice. I'm leaning towards spool, as they tend to be big, and > it would really be better not to erase them. Well, if you ask me, I think /var/cache doesn't look that bad for t