Thus spake Bernard Li ([EMAIL PROTECTED]):
Hi Brian:

I think the culprits are udev and hotplug, and it might stem from the
debian/rules, see:

cd
/usr/src/redhat/BUILD/systemimager-3.7.2r3463M_bli/initrd_source/src/hot
plug-0.0.20040329.orig && ./debian/rules clean | perl -pi -e 's/^/    /'
   make[1]: Entering directory
`/usr/src/redhat/BUILD/systemimager-3.7.2r3463M_bli/initrd_source/src/ho
tplug-0.0.20040329.orig'
   /usr/bin/make -f debian/sys-build.mk source.clean
   make[2]: Entering directory
`/usr/src/redhat/BUILD/systemimager-3.7.2r3463M_bli/initrd_source/src/ho
tplug-0.0.20040329.orig'
   make[3]: Entering directory
`/usr/src/redhat/BUILD/systemimager-3.7.2r3463M_bli/initrd_source/src/ho
tplug-0.0.20040329.orig/debian/scripts'
   make[3]: Leaving directory
`/usr/src/redhat/BUILD/systemimager-3.7.2r3463M_bli/initrd_source/src/ho
tplug-0.0.20040329.orig/debian/scripts'
   make[3]: Entering directory
`/usr/src/redhat/BUILD/systemimager-3.7.2r3463M_bli/initrd_source/src/ho
tplug-0.0.20040329.orig/debian/scripts'
   make[3]: Leaving directory
`/usr/src/redhat/BUILD/systemimager-3.7.2r3463M_bli/initrd_source/src/ho
tplug-0.0.20040329.orig/debian/scripts'
   make[2]: Leaving directory
`/usr/src/redhat/BUILD/systemimager-3.7.2r3463M_bli/initrd_source/src/ho
tplug-0.0.20040329.orig'
dh_clean
BTW, I needed to update udev to 079 otherwise it won't build on RHEL4,
also when I update to 079, it complained about not being able to build
udev with selinux support.

Is there a compeling reason why we're using the debian/ubuntu version of
udev, instead of the vanilla one? (I guess same goes to hotplug?)

Yes.  Vanilla udev and hotplug only provide tools, but with no
instructions to the system on how to use them.  As in, vanilla hotplug
and udev would be useless unless we wrote all of our own configuration
information.

That's what I started with, and that's why I chose to use an
implementation from a distribution that is considered to have good, and
fairly standardized, hardware detection and support.

I'll take a look this week at removing any remaining dh_* dependencies
in the build system.

Cheers, -Brian



Thanks,

Bernard

-----Original Message-----
From: Brian Elliott Finley [mailto:[EMAIL PROTECTED] Sent: Monday, March 20, 2006 11:07
To: Andrea Righi
Cc: Bernard Li; Sisuite-Dev
Subject: Re: [Fwd: RE: [Sisuite-devel] 3.7.2 hotplug]

If you're building these, and it's trying to invoke a dh_* script, then
I need to modify the build to not use them.

I've created patches or done perl/foo against other tarballs pulled from
ubuntu/debian source to eleminate the need for those.

I thought I had done that for all such packages, but perhaps not.
Are there any other packages that have this problem?

-Brian



Thus spake A Righi ([EMAIL PROTECTED]):
>Brian,
>
>a question for you about udev... :-)
>
>Cheers,
>-Andrea
>
>-------- Original Message --------
>Subject: RE: [Sisuite-devel] 3.7.2 hotplug
>Date: Sun, 19 Mar 2006 15:03:31 -0800
>From: Bernard Li <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>
>Sure - why don't we send an email to sisuite-devel and cc: Brian asking
>him about that.
>
>In the mean time, I'm building systemimager RPM on my system and copying
>the dh_* scripts to /usr/bin/ (this is just a test system, so I don't
>really care...)
>
>Cheers,
>
>Bernard
>
>________________________________
>
>From: Andrea Righi [mailto:[EMAIL PROTECTED]
>Sent: Sun 19/03/2006 14:48
>To: Bernard Li
>Subject: Re: [Sisuite-devel] 3.7.2 hotplug
>
>
>
>Bernard Li wrote:
>> Well, perhaps we only really need a handful of the commands, eg.
>> dh_clean and dh_testdir?
>>
>> Also, you really only need them during build. Perhaps we should not
>> use the debian/ubuntu udev and just build it from the original
>> source, in that way I don't think we'll be dependent on the debian
>> toolchain.
>>
>
>Yes, this is probably the cleaner way.. I don't know why Brian took the >debian release.. we can ask to him if there are side-effects using the
>defalut branch.
>
>Cheers,
>-Andrea
>
>-------- Original Message --------
>Subject: RE: [Sisuite-devel] 3.7.2 hotplug
>Date: Sun, 19 Mar 2006 14:33:13 -0800
>From: Bernard Li <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>
>Well, perhaps we only really need a handful of the commands, eg.
>dh_clean and dh_testdir?
>
>Also, you really only need them during build. Perhaps we should not use
>the debian/ubuntu udev and just build it from the original source, in
>that way I don't think we'll be dependent on the debian toolchain.
>
>Cheers,
>
>Bernard
>
>________________________________
>
>From: Andrea Righi [mailto:[EMAIL PROTECTED]
>Sent: Sun 19/03/2006 14:32
>To: Bernard Li
>Subject: Re: [Sisuite-devel] 3.7.2 hotplug
>
>
>
>All the dh_* commands seem to be perl script, so they could be
>integrated in systemimager without problems... maybe under the tools/
>directory, but I'd like to find a nicer and in particular a cleaner way
>to do that.
>
>Cheers,
>-Andrea
>
>Bernard Li wrote:
>> Hi Andrea:
>>
>> I couldn't find a deb RPM for Red Hat... Though I think this Debian
>package provides all the files we need:
>>
>> http://packages.debian.org/stable/devel/debhelper
>>
>> Would it be possible to build this as part of SystemImager but do not
>include the files?
>>
>> Cheers,
>>
>> Bernard
>>

--
Brian Elliott Finley
Mobile:  630.631.6621


--
Brian Elliott Finley
Mobile:  630.631.6621


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Sisuite-devel mailing list
Sisuite-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-devel

Reply via email to