(Greg: This gentlemen is interested in taking over the mandrake rpms,
and as I've neglected them recently I'd like to take him up on it. If
that is acceptable to you, could you set him up ? You could remove my
commit access as well, if you'd like.)
On Thu, Sep 18, 2003 at 12:56:04AM -0400, Files wrote:
> This is untrue. I can compile ANY Mandrake Linux SRPM without first
> creating a .rpmmacros file or a .rpmrc file. This is due to the fact
> that the Mandrake Linux RPM how-to which advocates is summarily
> ignored by Mandrake Linux SRPMS by using safe defaults.
That you can or can't is unimportant - that people can have their own
with their own data is important. My point was that I was not in favor
of your makefiles CREATING or MODIFYING said files. If they do not
then I don't have a problem with it.
Although, I have NEVER seen a spec file from mandrake that includes
the vendor, distribution, _signature, _topdir, _tmppath, _gpg_name or
_gpg_path macros. Those may have sane defaults in the system RPM
configuration, but I've never seen them in any of the spec files I've
derived/rebuilt from mandrake SRPMS.
If your goal is to be able to build these as mandrake rpms with any rpm
then I guess I can see why you're doing it that way.
> Secondly, .rpmrc contains build-arch translations. These translation
> are defined by Mandrake Linux. They do not change. They are not
> preferences. So putting them into a single file that is used in
> conjunction with all the default rc files
> (/usr/lib/rpm/rpmrc:/etc/rpmrc:~/.rpmrc) as well as the subversion
> version, subversion.rc automatically builds the package correctly.
It can contain a lot more then just build arch translations.
As I said initially, if you are not creating that file or modifying it
or somehow preventing the local file from taking precedance, then I am
neutral to the change.
> I have been testing this set of changes under Mandrake-9.1 Bamboo w/
> partial upgrades to 9.2rc2..
nodnod.
> I just know that I for one can't STAND having to CREATE a bunch of
> files, just to bootstrap something that I want to just use. It should
> *just work*.
I don't ever create a bunch of files - I have my rpm creation
environment setup on the machines I build RPMs on and I expect that when
I build rpm's they use my already setup environment. I would be
suprised, if not annoyed, if when I built an RPM it started putting crap
in /tmp or otherwise ignored my previous configuration directives.
I've never built a mandrake rpm that did that. If the directives in your
spec file override the ones in the local ~/.rpmmacros then, in my
opinion, I think that is bad. If they don't override the local settings
then I think it's fine.
That you can't stand setting a couple files up is one thing, but if for
your convenience you force someone else to change the spec file to
reflect their configuration then I think your convenience should take
second chair.
> Let me know what you think.....I won't pollute the dev mailing list
> with an unsanctioned SRPM, but I can send you one if you like.
Yeah - don't post srpms... :)
One way or another I'm fine if you want to take over maintaining those
files. I do not have the ability to let you commit, nor is it really my
place to say you can. I've CC'd Greg Stein directly though, he is who
set me up, hopefully he'll be able to set you up too.
--
Michael Ballbach, N0ZTQ
ballbach@rten.net -- PGP KeyID: 0xA05D5555
http://www.rten.net/
- application/pgp-signature attachment: stored
Received on Thu Sep 18 20:27:59 2003