Re: dpkg support for solaris-i386 architecture

2006-04-07 Thread Martin Wuertele
* Andrew Donnellan [EMAIL PROTECTED] [2006-04-06 23:19]: Or as Wouter pointed out on d-d port glibc. Which I think would be most beneficial as it additianaly would minimize the number of packages to add to the archive for the solaris port in case nexentas work should become a debian subproject

Re: dpkg support for solaris-i386 architecture

2006-04-07 Thread Andrew Donnellan
I suppose porting glibc is quite important because it also minimises the porting of everything else that may need to be adapted. andrew On 4/7/06, Martin Wuertele [EMAIL PROTECTED] wrote: * Andrew Donnellan [EMAIL PROTECTED] [2006-04-06 23:19]: Or as Wouter pointed out on d-d port glibc.

Re: dpkg support for solaris-i386 architecture

2006-04-06 Thread Andrew Donnellan
(d-l may give advice) So now that's sorted out really Nexenta needs an exemption from *every* copyright holder in dpkg, gcc, binutils, apt, coreutils, etc. (the GNU utils would be easier as there is _usually_ only one copyright holder: FSF) or OpenSolaris needs to relicense (impossible as Sun

Re: dpkg support for solaris-i386 architecture

2006-04-06 Thread Andrew Donnellan
Or as Wouter pointed out on d-d port glibc. andrew On 4/7/06, Andrew Donnellan [EMAIL PROTECTED] wrote: (d-l may give advice) So now that's sorted out really Nexenta needs an exemption from *every* copyright holder in dpkg, gcc, binutils, apt, coreutils, etc. (the GNU utils would be easier

Re: dpkg support for solaris-i386 architecture

2006-04-06 Thread Steve Langasek
On Thu, Apr 06, 2006 at 04:24:10PM -0700, Alex Ross wrote: Andrew Donnellan wrote: (d-l may give advice) So now that's sorted out really Nexenta needs an exemption from *every* copyright holder in dpkg, gcc, binutils, apt, coreutils, etc. (the GNU utils would be easier as there is

Re: dpkg support for solaris-i386 architecture

2006-04-06 Thread Russ Allbery
Steve Langasek [EMAIL PROTECTED] writes: On Thu, Apr 06, 2006 at 04:24:10PM -0700, Alex Ross wrote: GPLv3 is available at [1]. The draft removes ambiguities of GPLv2, and in particular, clarifies the old GPLv2 clause 3: You may copy and distribute the Program ... During the discussion [2],