ARCH is an optional argument anyway to common.postinst.
uname -m is not reliable in a buildd environment. If you don't provide ARCH
it does fall back to uname -m
On Tue, Dec 15, 2009 at 17:45, Anders Kaseorg <email address hidden> wrote:
> What’s wrong with ‘uname -m’? (Is this somehow related to allowing
> builds on a buildd?)
>
> But in any event, why can’t /usr/lib/dkms/common.postinst do the
> architecture detection itself? There’s no reason the module package
> itself should have to care about that detail.
>
> --
> Packages using DKMS should make use of /usr/lib/dkms/common.postinst
> https://bugs.launchpad.net/bugs/497149
> You received this bug notification because you are a member of Mythbuntu
> Developers, which is subscribed to lirc in ubuntu.
>
--
Mario Limonciello
<email address hidden>
Sent from Manchester, NH, United States
ARCH is an optional argument anyway to common.postinst.
uname -m is not reliable in a buildd environment. If you don't provide ARCH
it does fall back to uname -m
On Tue, Dec 15, 2009 at 17:45, Anders Kaseorg <email address hidden> wrote:
> What’s wrong with ‘uname -m’? (Is this somehow related to allowing dkms/common. postinst do the dkms/common. postinst /bugs.launchpad .net/bugs/ 497149
> builds on a buildd?)
>
> But in any event, why can’t /usr/lib/
> architecture detection itself? There’s no reason the module package
> itself should have to care about that detail.
>
> --
> Packages using DKMS should make use of /usr/lib/
> https:/
> You received this bug notification because you are a member of Mythbuntu
> Developers, which is subscribed to lirc in ubuntu.
>
--
Mario Limonciello
<email address hidden>
Sent from Manchester, NH, United States