Hello,
i have a package which provides a template config file.
It asks several debconf questions and generate a config file inside /etc
where all template variables was replaced with debconf responses.
After a package upgrade i want to check if the generated config file was
modified by user
Hello,
i have a package which provides a template config file.
It asks several debconf questions and generate a config file inside /etc
where all template variables was replaced with debconf responses.
After a package upgrade i want to check if the generated config file was
modified
On Fri, Oct 27, 2006 at 08:13:38AM +0900, Charles Plessy wrote:
Le Thu, Oct 26, 2006 at 03:30:50PM +0200, Thibaut Paumard a ?crit :
Charles Plessy [EMAIL PROTECTED] wrote:
Examples of packages which would be included in contrib are:
* free packages which require [...] packages which
On Sun, Oct 29, 2006 at 09:57:57PM +0100, Daniel Baumann wrote:
Marco Amadori wrote:
This seems to be against DFSG n# 8. License Must Not Be Specific to Debian
[0]
You're absolutely right.. for main, but not for non-free.
This is a matter for -legal, but anyway.
No, he's not right. The
On Mon, Oct 30, 2006 at 10:06:05AM +0100, Markus Schulz wrote:
After a package upgrade i want to check if the generated config file was
modified by user with a md5sum and ask the user if i can override the
existing config file (only if different) with the new generated
version.
But a read
Bas Wijnen wrote:
No, he's not right. The problem is that it violates DFSG #1, Free
Redistribution, in particular The license of a Debian component may not
restrict any party from selling or giving away the software
First of all, there is no source-code ;)
Anyway, let's do not nitpick..
Markus Schulz [EMAIL PROTECTED] writes:
Hello,
i have a package which provides a template config file.
It asks several debconf questions and generate a config file inside /etc
where all template variables was replaced with debconf responses.
After a package upgrade i want to check if
On Mon, 18 Sep 2006 04:33:49 -0700, Steve Langasek [EMAIL PROTECTED]
wrote:
The error is, if you don't *need* a specific version of the package, you
shouldn't depend on it at /all/. Essential means it's always available, so
there's no reason for you to depend on it.
I have never understood the
Dear mentors,
I am looking for a sponsor for the new version 0.7.5-2
of my package flamerobin.
It builds these binary packages:
flamerobin - graphical database administration tool for Firebird DBMS
The package is lintian/linda clean.
Changelog:
flamerobin (0.7.5-2) unstable; urgency=low
*
On Mon, Oct 30, 2006 at 01:06:08PM +0100, Marc Haber wrote:
On Mon, 18 Sep 2006 04:33:49 -0700, Steve Langasek [EMAIL PROTECTED]
wrote:
The error is, if you don't *need* a specific version of the package, you
shouldn't depend on it at /all/. Essential means it's always available, so
there's
Am Montag, 30. Oktober 2006 10:11 schrieb Michael Tautschnig:
Hello,
i have a package which provides a template config file.
It asks several debconf questions and generate a config file inside
/etc where all template variables was replaced with debconf
responses.
After a package
Le Mon, Oct 30, 2006 at 10:25:23AM +0100, Bas Wijnen a écrit :
Charles Plessy [EMAIL PROTECTED] wrote:
Does it mean that the upload of packages which can not be built or used
using commands like dpkg, apt, or aptitude, as opposed to make, is
discouraged?
I don't quite
On Mon, Oct 30, 2006 at 02:01:54PM +0100, Marc Haber wrote:
On Mon, Oct 30, 2006 at 01:59:05PM +0100, Bas Wijnen wrote:
Packages aren't moved out of essential.
So you can guarantee that bash will always be essential?
Certainly not. :-) I'm saying that we don't plan to ever make it
Hello Marcello,
On Sun, 2006-10-08 at 01:40 -0300, metal wrote:
On 9/28/06, Sandro Tosi [EMAIL PROTECTED] wrote:
I am looking for a sponsor for my package scuttle.
- many upstream files miss copyright notice: I think you should
ask upsteam to add that note (but I'd like to hear a DD
On Mon, 2006-10-30 at 14:31 +0200, Damyan Ivanov wrote:
* Added --as-needed to LDFLAGS to avoid unnecessary NEEDED entries.
Thanks to Christian 'Greek0' Aichinger.
Is the use of --as-needed encouraged/discouraged in Debian? Is there a
reason this isn't used system-wide? (I'm aware some
Richard Laager wrote:
On Mon, 2006-10-30 at 14:31 +0200, Damyan Ivanov wrote:
* Added --as-needed to LDFLAGS to avoid unnecessary NEEDED entries.
Thanks to Christian 'Greek0' Aichinger.
Is the use of --as-needed encouraged/discouraged in Debian? Is there a
reason this isn't used
Charles Plessy [EMAIL PROTECTED] writes:
I am working on a package which contains MSWord documents. I was wondering
the following questions:
1) How can I know if they are redistributable at all, for instance if
they contain non-free fonts? In the worst case, do I have to repackage
the
On Mon, Oct 30, 2006 at 02:01:54PM +0100, Marc Haber wrote:
On Mon, Oct 30, 2006 at 01:59:05PM +0100, Bas Wijnen wrote:
Packages aren't moved out of essential.
So you can guarantee that bash will always be essential?
I believe that we won't ever remove *functionality* from the Essential
[EMAIL PROTECTED] writes:
Hello Acid0,
Acid0,
Please don't touch the Subject:, since it may break the threading support
in reader programs. You reply to the Person, and the MUA can thread the
reply accordingly without touching the Subject:
Jari
--
To UNSUBSCRIBE, email to [EMAIL
On Mon, Oct 30, 2006 at 12:07:52PM -0600, Richard Laager wrote:
On Mon, 2006-10-30 at 14:31 +0200, Damyan Ivanov wrote:
* Added --as-needed to LDFLAGS to avoid unnecessary NEEDED entries.
Thanks to Christian 'Greek0' Aichinger.
Is the use of --as-needed encouraged/discouraged in
On Mon, 2006-10-30 at 19:30 +0100, Michael Biebl wrote:
http://lists.debian.org/debian-devel-announce/2005/11/msg00016.html
In short:
- First try the relibtoolize approach.
I'll start by admitting I don't know much about the autotools.
I took a look at this URL:
Steve Langasek [EMAIL PROTECTED] writes:
On Mon, Oct 30, 2006 at 02:01:54PM +0100, Marc Haber wrote:
On Mon, Oct 30, 2006 at 01:59:05PM +0100, Bas Wijnen wrote:
Packages aren't moved out of essential.
So you can guarantee that bash will always be essential?
I believe that we won't ever
[Richard Laager]
If I follow those steps, I'm making a bunch of changes in the source
directory of the package, which creates a big diff [1]. Is that
really the best way? Should I instead run those commands as part of
the package build process?
I do this stuff at build time.[1]
Many people
23 matches
Mail list logo
