Le 24/10/2012 00:04, Adam Williamson a écrit :
Would it be super-hard to just write a bot that does PEAR package builds
and updates? That seems like it'd mostly solve the problem.
Something like:
pear make-rpm-spec foo-1.2.3.tgz
rpmbuild -ba foo.spec
Yes, this is mostly automatic, but
On Wed, 2012-10-24 at 09:02 +0200, Remi Collet wrote:
Le 24/10/2012 00:04, Adam Williamson a écrit :
Would it be super-hard to just write a bot that does PEAR package builds
and updates? That seems like it'd mostly solve the problem.
Something like:
pear make-rpm-spec foo-1.2.3.tgz
For years... pear have its metadata database stored in /usr/share/pear
This will move soon to /var/lib/pear (to be FHS compliant).
(feature approved/merged by upstream)
With this last change, we'll have only libraries in /usr/share/pear
(which is part of the default php include_path)
WARNING :
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 23/10/2012 16:44, Reindl Harald a écrit :
does pear update pear this also know?
Currently we have latest pear 1.9.4 in fedora.
As this feature have been merged by upstream,
yes next version will be aware of this feature.
And pear, in fedora,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 23/10/2012 17:45, Reindl Harald a écrit :
because i never found all used packages as RPM
And ?
What are you waiting for ?
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.18 (GNU/Linux)
Comment: Using GnuPG with Mozilla -
Am 23.10.2012 16:40, schrieb Remi Collet:
For years... pear have its metadata database stored in /usr/share/pear
This will move soon to /var/lib/pear (to be FHS compliant).
(feature approved/merged by upstream)
With this last change, we'll have only libraries in /usr/share/pear
(which
Am 23.10.2012 17:38, schrieb Remi Collet:
in the real life mostly even as RPM packed pear packages are
updated with pear upgrade because the RPM's are way behind by
design
I disagree.
RPM maintainers keep a consistent PEAR stack and add more QA.
Before running any pear update ... you
Am 23.10.2012 17:57, schrieb Remi Collet:
Le 23/10/2012 17:45, Reindl Harald a écrit :
because i never found all used packages as RPM
And ?
What are you waiting for?
what should i wait for?
pear install whatever
pear itself is a package-system which should not be wrapped
in another one
On 10/23/2012 06:00 PM, Reindl Harald wrote:
Am 23.10.2012 17:57, schrieb Remi Collet:
Le 23/10/2012 17:45, Reindl Harald a écrit :
because i never found all used packages as RPM
And ?
What are you waiting for?
what should i wait for?
pear install whatever
pear itself is a
Am 23.10.2012 19:03, schrieb Matthias Runge:
On 10/23/2012 06:00 PM, Reindl Harald wrote:
Am 23.10.2012 17:57, schrieb Remi Collet:
Le 23/10/2012 17:45, Reindl Harald a écrit :
because i never found all used packages as RPM
And ?
What are you waiting for?
what should i wait for?
On 10/23/2012 08:40 AM, Remi Collet wrote:
For years... pear have its metadata database stored in /usr/share/pear
This will move soon to /var/lib/pear (to be FHS compliant).
(feature approved/merged by upstream)
With this last change, we'll have only libraries in /usr/share/pear
(which is part
On Tue, 2012-10-23 at 21:42 +0200, Reindl Harald wrote:
if ALL pear packages would be in the repos this whould be
a diffeent story - but taht is unlikely because who
would maintain all this packages really?
It seems like something that should be automatable, really. Don't we
already have
On Wednesday, October 24, 2012 06:04 AM, Adam Williamson wrote:
On Tue, 2012-10-23 at 21:42 +0200, Reindl Harald wrote:
if ALL pear packages would be in the repos this whould be
a diffeent story - but taht is unlikely because who
would maintain all this packages really?
It seems like
Le 23/10/2012 23:02, Nathanael D. Noblet a écrit :
I presume php-pecl packages are un-affected by this?
Right.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
14 matches
Mail list logo
