[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Can/should we have an efi/efi-any platform architecture?



Quoting Joachim Breitner (2014-12-12 13:55:24)
> Am Freitag, den 12.12.2014, 12:07 +0000 schrieb Wookey:
>> +++ Sebastian Reichel [2014-12-11 21:25 +0100]:
>>> How about building for "arch: any" and adding a build dependency on 
>>> a new "efi-support" package, that is only available for 
>>> architectures with efi available?
>
> I was about to suggest the same thing.
>
>> That is a sensible suggestion. It keeps the ecosystem of 'efi stuff' 
>> more self-contained than involving dpkg. If it was expected to change 
>> frequently this would probably work better in practice.
>
> that’s what the Haskell packages to. Some require a certain feature 
> that is not available on all arches, and a virtual packages provided 
> only on those arches (ghc-ghci) is used in the Build-Depends. Works 
> great, and once a new architecture gets added, all packages are 
> automatically built.

Are those features tied to hardware?  Could you provide some examples?


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

Attachment: signature.asc
Description: signature


Reply to: