some sort of virtual kernel package that I can make
use of to describe that my package depends on a 2.6 kernel to be
installed but not a specific image.
Another possibility would just be to drop any dependency of a specific
kernel image.
Any suggestions/comments will be welcome.
Regards.
Lars Roland.
system is installed correctly. This will ensure
that the source package will compile on any system.
3) Ship the configured kernel source along with the package (crappy
solution - but it will of cause work).
Any feedback (or even solutions) will be appreciated.
Regards.
Lars Roland
On Tue, 08 Mar 2005 15:07:33 -0800, Russ Allbery <[EMAIL PROTECTED]> wrote:
> It doesn't really matter, at least to Debian, since it's not for inclusion
> in the Debian archive, but for the record this is not a correct
> understanding of the license on qmail. It is not covered under the
> Artistic
On Tue, 08 Mar 2005 16:48:09 +0100, Sven Mueller <[EMAIL PROTECTED]> wrote:
> In this case, you can't use Provides:. dpkg doesn't allow versioned
> depends to be resolved by Provides: (and doesn't support versions in the
> Provides: statement either). You package is named qmail and the package
> yo
On Tue, 8 Mar 2005 08:50:13 -0500, Justin Pryzby
<[EMAIL PROTECTED]> wrote:
> You can uses a Provides: in the control file (providing a non-virtual
> package).
>
> http://www.debian.org/doc/debian-policy/ch-relationships.html
>
> Justin
It is a little more complex than that
The original pack
On Tue, 8 Mar 2005 07:38:12 -0600 (CST), elijah wright <[EMAIL PROTECTED]>
wrote:
> uhh - isn't qmail one of those packages that is licensed in such a way
> that you are NOT allowed to distribute patched binary builds or patched
> source?
>
> just a vague recollection, here... isn't that DJB's st
?.
Regards.
Lars Roland
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Tue, 1 Mar 2005 16:51:02 +0100, Romain Beauxis <[EMAIL PROTECTED]> wrote:
> Le Mardi 1 Mars 2005 16:34, Lars Roland a écrit :
> > 2) When you update the database software from, say, version 1.0 to 1.1
> > then it would be preferable to NOT generate all the tables again (th
Hi
This may be newbie questions, but anyway here goes: We have a
commercial system, that we are planing to make available open source
(GPL) - right now the plan is to have deb packages and tgz files for
the installation. The tgz installation can be broken into
a) Executable files
b) Database f
9 matches
Mail list logo
