naming packages installed to /usr/share/pear

2010-10-01 Thread Elan Ruusamäe 
  nowadays pear package has lost it's meaning of being code hosted at 
http://pear.php.net/

there seems to be coming larger amount of packages that are suggested to 
be installed using pear command

http://www.phpunit.de/manual/current/en/installation.html
http://www.ezcomponents.org/
http://pear.horde.org/
... (see php-pear.spec for channel defs)

the package naming rules should be unfied, because 
php-pear-PEAR_Command_Packaging not only creates new .spec files, but 
also creates depdendencies based on that info.

currently pear make-rpm-spec decides (and seems work farily well):
- if package cames from pear channel, name it php-pear-%{pkgname}
- if cames elsewhere, name it as php-%{pkgname}
- if it is source package, it will be named as php-pecl-%{pkgname}

does anybody see problem with this pattern?
should the pear-channel packages renamed also to php-%{pkgname}

and what to do with ezcomponents.spec,
drop it and build each package from separate spec?

similar package is php-seclib.spec, which initially packages whole 
channel, should each of them be created own .spec?

if ezcomponents.spec and php-seclib.spec aren't split to package specs, 
should it P: names if they would?

-- 
glen

___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en

Re: kernel-xenU on non-64bit EC2 instance

2010-10-01 Thread Paweł Zuzelski 
On Fri, 01 Oct 2010, Caleb Maclennan wrote:
> Alright guys I'm lost. I've been poking around in specs trying to
> figure this out and can't make out what I'm supposed to use or what I
> need to work on if there isn't the right thing available.
> 
> I am trying to maintain several TH machines on i386 instances over on
> EC2. They have recently opened up their systems to running custom
> kernels inside the instance using pv-grub. I can't figure out what pld
> kernel package to use for this.
> 
> The kernel-xenU package is set to x86_64 only?

Yes, that is because I use xen domU on x86_64 machines only. If you
need xen domU on i686, feel free to add this arch to
kernel-xenU.spec. Any help with this spec will be appreciate.

> The kernel-xen package was last maintained in 2008?

Yes, it is obsolte.

> The kernel package doesn't have xen block drivers.

Yes, other kernels are compiled without xen domU support. Use
kernel-xenU.spec (and please, help to develop/test it on 32 archs).

-- 
Paweł
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en

kernel-xenU on non-64bit EC2 instance

2010-10-01 Thread Caleb Maclennan 
Alright guys I'm lost. I've been poking around in specs trying to
figure this out and can't make out what I'm supposed to use or what I
need to work on if there isn't the right thing available.

I am trying to maintain several TH machines on i386 instances over on
EC2. They have recently opened up their systems to running custom
kernels inside the instance using pv-grub. I can't figure out what pld
kernel package to use for this.

The kernel-xenU package is set to x86_64 only?

The kernel-xen package was last maintained in 2008?

The kernel package doesn't have xen block drivers.

What path should I be pursuing here?

Caleb
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en