On Sat, Nov 01, 2008 at 07:29:16PM -0400, Filipus Klutiero wrote:
>> | Package: test
>> | Depends: test-modules | test-source
>> |
>> | Package: test-modules
>> | Depends: linux-image-2.6.26-1-powerpc | linux-image-2.6.26-1-powerpc64
>> |
>> | Package: test-source
>>
>> Both apt and aptitude woul
On Sat, Nov 01, 2008 at 09:37:50PM +0100, Frans Pop wrote:
> For a really neat and complete solution you'd IMO still need something
> like I proposed though to make the vbox ABI visible in package names, but
> that can probably be postponed until after Lenny.
Well it is, namely the upstream vers
On Sat, Nov 01, 2008 at 07:29:16PM -0400, Filipus Klutiero wrote:
>> | Package: test
>> | Depends: test-modules | test-source
>> |
>> | Package: test-modules
>> | Depends: linux-image-2.6.26-1-powerpc | linux-image-2.6.26-1-powerpc64
>> |
>> | Package: test-source
>>
>> Both apt and aptitude would
Hi folks
Because of some recent events, I thought about the possibility for
packages to depend against kernel module packages. As we don't want to
dictate the usage of Debian provided kernels, we need a last resort
fallback to the modules source.
My first solution was something like the followi
On Sat, Nov 01, 2008 at 08:41:46PM +0100, Michael Meskes wrote:
> On Fri, Oct 31, 2008 at 07:48:41PM +0100, Frans Pop wrote:
> > I guess one solution could be to have virtualbox-ose not depend on
> > virtualbox-modules, but on virtualbox-ose-modules-$ABI.
> Building vbox modules from lme makes no
Michael Meskes wrote:
> On Fri, Oct 31, 2008 at 07:48:41PM +0100, Frans Pop wrote:
>> I guess one solution could be to have virtualbox-ose not depend on
>> virtualbox-modules, but on virtualbox-ose-modules-$ABI.
>
> Building vbox modules from lme makes no real sense to me because lme is
> not supp
On Fri, Oct 31, 2008 at 07:48:41PM +0100, Frans Pop wrote:
> I guess one solution could be to have virtualbox-ose not depend on
> virtualbox-modules, but on virtualbox-ose-modules-$ABI.
Building vbox modules from lme makes no real sense to me because lme is not
supposed to be reupped for each new
Bastian Blank wrote:
> On Fri, Oct 31, 2008 at 05:07:44PM +0100, Frans Pop wrote:
>> Exactly because of the option of using custom built kernels, virtualbox
>> does not depend on the Debian modules packages, but only recommends
>> them (which IMO is correct: the Debian module package will be instal
On Fri, Oct 31, 2008 at 05:07:44PM +0100, Frans Pop wrote:
> Bastian Blank wrote:
> > Because of some recent events, I thought about the possibility for
> > packages to depend against kernel module packages. As we don't want to
> > dictate the usage of Debian provided kernels, we need a last resort
Bastian Blank wrote:
> Because of some recent events, I thought about the possibility for
> packages to depend against kernel module packages. As we don't want to
> dictate the usage of Debian provided kernels, we need a last resort
> fallback to the modules source.
Exactly because of the option o
On Friday 31 October 2008 22:20:26 Josselin Mouette wrote:
> Le vendredi 31 octobre 2008 à 12:44 +0100, Bastian Blank a écrit :
> > Because of some recent events, I thought about the possibility for
> > packages to depend against kernel module packages. As we don't want to
> > dictate the usage of
Le vendredi 31 octobre 2008 à 12:44 +0100, Bastian Blank a écrit :
> Because of some recent events, I thought about the possibility for
> packages to depend against kernel module packages. As we don't want to
> dictate the usage of Debian provided kernels, we need a last resort
> fallback to the mo
Hi folks
Because of some recent events, I thought about the possibility for
packages to depend against kernel module packages. As we don't want to
dictate the usage of Debian provided kernels, we need a last resort
fallback to the modules source.
My first solution was something like the following
13 matches
Mail list logo
