I just have a look to the perl module code we provide with rpm5, and I'd like
to massivelly rework it:
- namespace seems inconsitent
- some useless #ifdef RPM41 (we don't have to deal with different version of
RPM)
- some non working old code.
- only one source file (splitting would help
Hmmm, on a rpm-4_5 checkout, I'm seeing this
$ ./devtool prepare
=== db (cvs co HEAD)
Enter passphrase for key '/home/jbj/.ssh/id_dsa':
cvs checkout: Updating db
U db/LICENSE
U db/README
cvs checkout: Updating db/btree
even though I'm trying to check out on the
On Jul 27, 2007, at 3:16 AM, Ralf S. Engelschall wrote:
Does anyone mind if I rework it completly ?
Go for it! I guess everyone is happy if you investigate on the perl/
subdir and make it working out-of-the-box under --with-perl. I even
would suggest that you _merge in_ your RPM4 API into
On Fri, Jul 27, 2007, Jeff Johnson wrote:
Hmmm, on a rpm-4_5 checkout, I'm seeing this
$ ./devtool prepare
=== db (cvs co HEAD)
Enter passphrase for key '/home/jbj/.ssh/id_dsa':
cvs checkout: Updating db
U db/LICENSE
U db/README
cvs checkout: Updating db/btree
On Jul 27, 2007, at 11:22 AM, Ralf S. Engelschall wrote:
I've sync'ed the devtool stuff with HEAD and I don't see why this
happens?
I can easily live with
for d in db file lua zlib; do cd $d cvs up -r rpm-4.5 -d -P;
cd ..; done
for building rpm-4.5 packages. rpm.spec hackery is
On Jul 27, 2007, at 12:21 PM, Jeff Johnson wrote:
Digging ...
My brain fart, too many windows, too many versions, too many
machines ...
73 de Jeff
__
RPM Package Manager
Because I get tired of looking at same old rpm -qa sopew, I usually
run a tricked up queryformat that looks much like a package file name.
One of the consequences of that is I end up looking at different
rpm -qa spewage than y'all.
So I just noticed
libXinerama-devel-1.0.2-1.fc7.i386
Now that I actually have my brain fart under control, db-4.6.18 is
headed
back onto HEAD this weekend.
I can trivially bundle that into rpm-4.5 and expect no problems.
The reason for doing so is to avoid doing so is the
tedious flip-flopping between Berkeley DB versions.
Any reservations on
On Thursday, 26 July 2007, at 11:55:35 (-0400),
Jeff Johnson wrote:
Read rpmrc files or not?
Not. It's a minimal compatibility gain for a big step backward. We
should try to get as close as possible out-of-the-box in terms of
platform portability, but there are better ways of doing it.
On Jul 27, 2007, at 2:17 PM, Michael Jennings wrote:
On Thursday, 26 July 2007, at 11:55:35 (-0400),
Jeff Johnson wrote:
Read rpmrc files or not?
Not. It's a minimal compatibility gain for a big step backward. We
should try to get as close as possible out-of-the-box in terms of
platform
On Jul 27, 2007, at 2:01 PM, Robert Scheck wrote:
On Fri, 27 Jul 2007, Jeff Johnson wrote:
Any reservations on bundling db-4.6.18 into db-4.5?
Assuming you mean rpm-4.5 rather db-4.5, otherwise this sentence
doesn't
make sense to me.
Yes. Watch for me to type db-2.6 rather than
On Jul 27, 2007, at 4:44 PM, Michael Jennings wrote:
On Wednesday, 11 July 2007, at 11:40:15 (+0200),
Michael Schroeder wrote:
Uh, not 002 please, 022 is the standard. Make it configurable if you
really need to do something like that.
Wouldn't this prevent the creation of group-writable
Le vendredi 27 juillet 2007, Jeff Johnson a écrit :
On Jul 27, 2007, at 3:16 AM, Ralf S. Engelschall wrote:
Does anyone mind if I rework it completly ?
Go for it! I guess everyone is happy if you investigate on the perl/
subdir and make it working out-of-the-box under --with-perl. I even
On Saturday, 30 June 2007, at 00:56:01 (-0500),
Tim Mooney wrote:
I would prefer that over the scenario I'm afraid we're heading for
too. The question is, what shiny features will ISVs clamor for?
Something to turn instroot tarballs/images into RPM's?
Michael
--
Michael Jennings (a.k.a.
On Friday, 27 July 2007, at 16:46:43 (-0400),
Jeff Johnson wrote:
But 0022 is the default setting, certainly choosing the uglix
standard default is the least surprising choice that meets the
largest number of expectations.
On systems that use UPG, 0002 is the default. And last time I used
On Jul 27, 2007, at 7:15 PM, Michael Jennings wrote:
Something to turn instroot tarballs/images into RPM's?
Been on my todo list since November 2005, no worry.
Adding tar payloads was just proof-of-concept ...
73 de Jeff
On Jul 27, 2007, at 7:20 PM, Michael Jennings wrote:
On Friday, 27 July 2007, at 16:46:43 (-0400),
Jeff Johnson wrote:
But 0022 is the default setting, certainly choosing the uglix
standard default is the least surprising choice that meets the
largest number of expectations.
On systems
On Wednesday, 18 July 2007, at 21:35:47 (+0200),
Thomas Lotterer wrote:
The first big looser was SVN which I ignored in the early days just
because I did not trust to put my data in this kind of storage.
Then you were foolish. Subversion's BDB backend had its issues, but
data integrity (at
On Wednesday, 18 July 2007, at 23:20:40 (+0200),
Ralf S. Engelschall wrote:
Can you be more specific, please? What _particular_ problems in
download scripts and in .spec files are you talking about here?
1. Downloading sources based on spec file names
2. rpmbuild -ta tarball, in which
19 matches
Mail list logo
