Hi,
On Fri, Nov 10, 2006 at 05:59:07PM -0800, Steve Langasek wrote:
...
> > Option 3)
> > * Set "Architecture: alpha amd64 arm hppa i386 ia64 m68k mips mipsel
> > powerpc sparc"
> > * Ask ftp-master for removal of package for s390
> > * Make entry in quinn-diff not to build on s390
>
> This is an acceptable solution,
...
> > Option 4)
> > * Set "Architecture: any"
> > * Have fancy script to fail in s390.
> > * Ask ftp-master for removal of package for s390
> > * Make entry in quinn-diff not to build on s390
>
> This is an acceptable solution.
I like the latter so I do not interfare with builoding kfreebsd-i386 etc.
...
> > PS: Many device support packages are almost useless for
> > non-PC/workstation like hardware. This goes with arm and mips too.
>
> No, you're missing the point. The S/390 port has *no hardware*; in the case
> of other architectures, some user *may* hook a synaptics device up to their
> computer, but on s390 this is not possible at all because of what s390 is.
> Even if the S/390 VM was enhanced somehow to support hooks for this class of
> physical hardware, the kernel has no support for it.
Considering ease of implimentation, I will be likely to end up with
Option 3. But for kfreebsd-i386 port etc., may be Option 4 is better.
I did some search on how other packages which are likely to face similar
issues by checking likely packages under laptop task and other random
packages which seems to be hardware specific which came to my mind. (I
did not check kernel support for acpi in the source for s390. cpufreq
doc seems to suggest no support for s390)
source Architecture s390-binary
acpi i386 ia64 amd64 no
acpi-support i386 ia64 amd64 no
acpid i386 ia64 amd64 no
hibernate all (no)
hotkey-setup i386 amd64 no
uswsusp i386 amd64 no
xserver-xorg-input-synaptics itemized w/o s390 no
toshset i386 no
toshutils i386 no
tpctl i386 no
thinkpad-base i386 no
thinkpad-source i386 no
motioneye i386 no
i810switch i386 kfreebsd-i386 no
spicctrl i386 no
rsjog i386 no
sjog i386 no
But...
source Architecture s390-binary
apmd any yes
cpufrequtils any yes
pcmciautils any yes
sensors-applet any yes
tpconfig any yes
wireless-tools any yes
wmbattery any yes
Hmmmm I have to do the same for tpconfig since it is also my package.
But none of these with any packages uses Option 4 so I can not take easy
example. (Maybe they deserve bug reports.)
Do I use this line in buid script?
if [ `dpkg-architecture -qDEB_BUILD_ARCH` = "s390" ]; then exit 1; fi
Osamu
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
