* Giorgio Pioda <[EMAIL PROTECTED]> [070513 14:12]:
> 1) The icons used by qgfe are taken from the following *.rpm:
> menu-icons-default-0.1-alt2.noarch.rpm
> which is distributed under GPL licence. Is it
> a problem? (I didn't succeed in finding the copyright of the icons, but
> I may resolve this
On Sun, 13 May 2007 14:11:48 +0200
Giorgio Pioda <[EMAIL PROTECTED]> wrote:
> Hallo mentors,
>
> I've packaged qgfe and is now almost mature, downloadable at:
>
> http://web.ticino.com/gfwp/debian/qgfe-1.0/
The location of the .dsc file is what mentors need:
http://web.ticino.com/gfwp/debian/qgfe
Hallo mentors,
I've packaged qgfe and is now almost mature, downloadable at:
http://web.ticino.com/gfwp/debian/qgfe-1.0/
I still have 2 questions about it:
1) The icons used by qgfe are taken from the following *.rpm:
menu-icons-default-0.1-alt2.noarch.rpm
which is distributed under GPL licence
On Sat, Apr 21, 2007 at 09:20:23AM -0700, John Stamp wrote:
> Franz and I agree that replacement is the better option. The newest
> lastfm client should remain "lastfm".
>
> How do I proceed? If I were starting a new package, I'd retitle
> #413271 to ITP etc., but that doesn't seem right in
The current maintainer for "lastfm" has given me permission to take
over the package. But there is also this RFP for "lastfm-client":
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=413271
Franz and I agree that replacement is the better option. The newest
lastfm client should remain "last
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
> 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
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,
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
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
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
Justin Pryzby wrote:
If you want a non-conffile configuration file, then you must not
provide the file in the package. Instead, create the file at install
time (not compile time) with the maintainer scripts (postinst
usually). If its a complicated file, store a template in
/usr/share/pkgnamehere/
If you want a non-conffile configuration file, then you must not
provide the file in the package. Instead, create the file at install
time (not compile time) with the maintainer scripts (postinst
usually). If its a complicated file, store a template in
/usr/share/pkgnamehere/...
Justin
On Sun, A
Florent Rougon wrote:
Shachar Shemesh <[EMAIL PROTECTED]> wrote:
two questions:
1. My package has a password file. Where is the best place to store it?
/etc/name/password? /var/lib/name/password?
If the password file is a system configuration file (i.e., a file that
can be customized by the
Shachar Shemesh <[EMAIL PROTECTED]> wrote:
> two questions:
> 1. My package has a password file. Where is the best place to store it?
> /etc/name/password? /var/lib/name/password?
If the password file is a system configuration file (i.e., a file that
can be customized by the admin to modify the
two questions:
1. My package has a password file. Where is the best place to store it?
/etc/name/password? /var/lib/name/password?
2. I have placed some file names into debian/conffiles. It seems,
however, that all files under /etc are logically added to it as well.
Files under /etc that I expli
On Thu, Dec 04, 2003 at 08:46:49PM +0100, Mattia Dongili wrote:
> > I don't understand. You seem to be saying that the headers you need are
> > not in the package, but also are in the package.
> >
> > "the source package needs some X headers not included in xlibs-dev"
> > and
> > "I'd set build d
On Thu, Dec 04, 2003 at 08:46:49PM +0100, Mattia Dongili wrote:
> > I don't understand. You seem to be saying that the headers you need are
> > not in the package, but also are in the package.
> >
> > "the source package needs some X headers not included in xlibs-dev"
> > and
> > "I'd set build d
On Thu, Dec 04, 2003 at 01:06:02PM -0500, Branden Robinson wrote:
> On Thu, Dec 04, 2003 at 02:10:42PM +0100, Mattia Dongili wrote:
[...]
> > Any suggestion about the name?
>
> xfree86-driver-synaptics-utils, maybe? Kind of long and ugly, but
> highly consistent with its counterpart.
I agree, it
On Thu, Dec 04, 2003 at 01:06:02PM -0500, Branden Robinson wrote:
> On Thu, Dec 04, 2003 at 02:10:42PM +0100, Mattia Dongili wrote:
[...]
> > Any suggestion about the name?
>
> xfree86-driver-synaptics-utils, maybe? Kind of long and ugly, but
> highly consistent with its counterpart.
I agree, it
On Thu, Dec 04, 2003 at 02:10:42PM +0100, Mattia Dongili wrote:
> 1- the upstream package contains also 2 extra utilities to enable
> runtime configuration of the driver (synclient and syndaemon). I'd
> package them separately and Recommend the utilities from the driver
> package. Is it the correct
On Thu, Dec 04, 2003 at 02:10:42PM +0100, Mattia Dongili wrote:
> 1- the upstream package contains also 2 extra utilities to enable
> runtime configuration of the driver (synclient and syndaemon). I'd
> package them separately and Recommend the utilities from the driver
> package. Is it the correct
Hi all,
I started packaging the synaptics touchpad driver[1] and I have a
couple of issues:
1- the upstream package contains also 2 extra utilities to enable
runtime configuration of the driver (synclient and syndaemon). I'd
package them separately and Recommend the utilities from the driver
pack
Hi all,
I started packaging the synaptics touchpad driver[1] and I have a
couple of issues:
1- the upstream package contains also 2 extra utilities to enable
runtime configuration of the driver (synclient and syndaemon). I'd
package them separately and Recommend the utilities from the driver
pack
24 matches
Mail list logo
