Re: automatic ~/rpmbuild by default rather than /usr/src/rpm etc..
On Mar 4, 2009, at 11:58 PM, Per Øyvind Karlsen wrote: Well, it's anyways a better default than what is currently, which makes it favorable IMO. How is having 2 or more defaults better? Truly whatever configuration is in the @rpm5.org tarball is not the default for anything, there's too many ways RPM configuration ( and usage) changes depending on how rpm is built. Feel free to add whatever configuration changes you wish to a devtool stanza, that's what is supposed to happen if you want to build rpm with a different default. 73 de Jeff __ RPM Package Managerhttp://rpm5.org Developer Communication Listrpm-devel@rpm5.org
Re: automatic ~/rpmbuild by default rather than /usr/src/rpm etc..
2009/3/3 Jeff Johnson n3...@mac.com
On Mar 3, 2009, at 6:36 AM, Per Øyvind Karlsen wrote:
2009/3/3 Anders F Björklund a...@rpm5.org
Per Øyvind Karlsen wrote:
I did the other day a fresh mandriva cooker install and noticed with rpm
4.6.0 a welcomed
change, the automatic creation and use of a local ~/rpmbuild for user
rather than /usr/src/rpm.
Since this makes it easier to just get a working rpm build environment
for user and also
removes the implicit encouragement of packaging using /usr/src/rpm as
root, would anyone
have anything against introducing same behaviour as rpm.org in rpm5.orgHEAD?
You can set that with the --with-path-sources configure option, if
scared of ~/.rpmmacros. I believe rpm.org uses %{getenv:HOME}/rpmbuild
Yes, but what I also would like is the automatic creation of these
directories as well.
Everything except the automatic/lazy creation of %{_topdir} has existed in
RPM for years IIRC. I certainly use some variant of the lazy creation daily
while building packages in
/X/%{NAME}
There's also the --with-path-buildroot option, if you also want to
change %{_tmppath} for %{_topdir}/BUILDROOT like rpm.org does now.
Not sure that the default configuration matters all that much, as
just with the rpm.spec it's bound to be changed by vendors anyway ?
Yes, to some degree, but if you provide a default for local users, the
default
will more likely be adopted and I can't see any reason why anyone would
feel
very strongly about changing such a default.
Having this as a default which user can expect to find ~regardless of
vendor seems like a
convenient way to make life easier for users and for anyone helping out
users..
There's serious flaws in the logic above. Sure, lusers are sheep likely
to do whatever is suggested as default. But that doesn't mean one
should just go around herding the sheep into other pastures for no
useful purpose.
If you like the @rpm.org model, by all means, use it. But recommending
that as default to everone is just pointless imho.
On Mar 3, 2009, at 6:36 AM, Per Øyvind Karlsen wrote:
2009/3/3 Anders F Björklund a...@rpm5.org
Per Øyvind Karlsen wrote:
I did the other day a fresh mandriva cooker install and noticed with rpm
4.6.0 a welcomed
change, the automatic creation and use of a local ~/rpmbuild for user
rather than /usr/src/rpm.
Since this makes it easier to just get a working rpm build environment
for user and also
removes the implicit encouragement of packaging using /usr/src/rpm as
root, would anyone
have anything against introducing same behaviour as rpm.org in rpm5.orgHEAD?
You can set that with the --with-path-sources configure option, if
scared of ~/.rpmmacros. I believe rpm.org uses %{getenv:HOME}/rpmbuild
Yes, but what I also would like is the automatic creation of these
directories as well.
Everything except the automatic/lazy creation of %{_topdir} has existed in
RPM for years IIRC. I certainly use some variant of the lazy creation daily
while building packages in
/X/%{NAME}
There's also the --with-path-buildroot option, if you also want to
change %{_tmppath} for %{_topdir}/BUILDROOT like rpm.org does now.
Not sure that the default configuration matters all that much, as
just with the rpm.spec it's bound to be changed by vendors anyway ?
Yes, to some degree, but if you provide a default for local users, the
default
will more likely be adopted and I can't see any reason why anyone would
feel
very strongly about changing such a default.
Having this as a default which user can expect to find ~regardless of
vendor seems like a
convenient way to make life easier for users and for anyone helping out
users..
There's serious flaws in the logic above. Sure, lusers are sheep likely
to do whatever is suggested as default. But that doesn't mean one
should just go around herding the sheep into other pastures for no
useful purpose.
If you like the @rpm.org model, by all means, use it. But recommending
that as default to everone is just pointless imho.
Well, it's anyways a better default than what is currently, which makes it
favorable IMO.
--
Regards,
Per Øyvind
Re: automatic ~/rpmbuild by default rather than /usr/src/rpm etc..
On Tue, Mar 3, 2009 at 11:38 AM, Per Øyvind Karlsen pkarl...@rpm5.orgwrote: I did the other day a fresh mandriva cooker install and noticed with rpm 4.6.0 a welcomed change, the automatic creation and use of a local ~/rpmbuild for user rather than /usr/src/rpm. Since this makes it easier to just get a working rpm build environment for user and also removes the implicit encouragement of packaging using /usr/src/rpm as root, would anyone have anything against introducing same behaviour as rpm.org in rpm5.orgHEAD? I agreed that it is a nice feature for a luser, as i am for example. But in rpm5.org there are some many nice feature, some present from a long time, mostly useful for a good distro and for a sysadmin. In fact many are requested today from the developer of fedora - just for example the rollback support -dropped from rpm4.6, runtime probe, parent dir e filelinkto deps, the full portability with so much platform - included RHEL4, RHEL5 where rpm4.6 is not - if ever - portable. So do you think it is nice to port these feature into rpm.org ? If yes, why exists in first place the rpm.org - rpm5.org duality ? But everyone know already. Regards
Re: automatic ~/rpmbuild by default rather than /usr/src/rpm etc..
On Mar 3, 2009, at 6:36 AM, Per Øyvind Karlsen wrote:
2009/3/3 Anders F Björklund a...@rpm5.org
Per Øyvind Karlsen wrote:
I did the other day a fresh mandriva cooker install and noticed with
rpm 4.6.0 a welcomed
change, the automatic creation and use of a local ~/rpmbuild for
user rather than /usr/src/rpm.
Since this makes it easier to just get a working rpm build
environment for user and also
removes the implicit encouragement of packaging using /usr/src/rpm
as root, would anyone
have anything against introducing same behaviour as rpm.org in
rpm5.org HEAD?
You can set that with the --with-path-sources configure option, if
scared of ~/.rpmmacros. I believe rpm.org uses %{getenv:HOME}/
rpmbuild
Yes, but what I also would like is the automatic creation of these
directories as well.
Everything except the automatic/lazy creation of %{_topdir} has
existed in
RPM for years IIRC. I certainly use some variant of the lazy creation
daily
while building packages in
/X/%{NAME}
There's also the --with-path-buildroot option, if you also want to
change %{_tmppath} for %{_topdir}/BUILDROOT like rpm.org does now.
Not sure that the default configuration matters all that much, as
just with the rpm.spec it's bound to be changed by vendors anyway ?
Yes, to some degree, but if you provide a default for local users,
the default
will more likely be adopted and I can't see any reason why anyone
would feel
very strongly about changing such a default.
Having this as a default which user can expect to find ~regardless
of vendor seems like a
convenient way to make life easier for users and for anyone helping
out users..
There's serious flaws in the logic above. Sure, lusers are sheep likely
to do whatever is suggested as default. But that doesn't mean one
should just go around herding the sheep into other pastures for no
useful purpose.
If you like the @rpm.org model, by all means, use it. But recommending
that as default to everone is just pointless imho.
73 de Jeff
Re: automatic ~/rpmbuild by default rather than /usr/src/rpm etc..
On Tue, Mar 3, 2009 at 3:14 PM, Jeff Johnson n3...@mac.com wrote:
On Mar 3, 2009, at 6:36 AM, Per Øyvind Karlsen wrote:
2009/3/3 Anders F Björklund a...@rpm5.org
Per Øyvind Karlsen wrote:
I did the other day a fresh mandriva cooker install and noticed with rpm
4.6.0 a welcomed
change, the automatic creation and use of a local ~/rpmbuild for user
rather than /usr/src/rpm.
Since this makes it easier to just get a working rpm build environment
for user and also
removes the implicit encouragement of packaging using /usr/src/rpm as
root, would anyone
have anything against introducing same behaviour as rpm.org in rpm5.orgHEAD?
You can set that with the --with-path-sources configure option, if
scared of ~/.rpmmacros. I believe rpm.org uses %{getenv:HOME}/rpmbuild
Yes, but what I also would like is the automatic creation of these
directories as well.
Everything except the automatic/lazy creation of %{_topdir} has existed in
RPM for years IIRC. I certainly use some variant of the lazy creation daily
while building packages in
/X/%{NAME}
Yep. I forget to tell this. RPM5 have already the nice, but not so new,
rpm.org feature of automatic build creation.
For example
[t...@rhel5 ~]$ id
uid=10002(test) gid=10002(test) gruppi=10002(test)
context=root:system_r:unconfined_t:SystemLow-SystemHigh
[t...@rhel5 ~]$ ls -la * NO L DIRECTORY NOTICE
totale 88
drwx-- 3 test test 4096 3 mar 18:10 .
drwxr-xr-x 6 root root 4096 3 mar 18:05 ..
-rw--- 1 test test 214 3 mar 18:05 .bash_history
-rw-r--r-- 1 test test 33 3 mar 18:05 .bash_logout
-rw-r--r-- 1 test test 176 3 mar 18:05 .bash_profile
-rw-r--r-- 1 test test 124 3 mar 18:05 .bashrc
-rw-r--r-- 1 test test 515 3 mar 18:05 .emacs
drwxr-xr-x 4 test test 4096 3 mar 18:05 .mozilla
-rw-r--r-- 1 test test 383 3 mar 18:05 .rpmmacros
-rw--- 1 test test 1102 3 mar 18:10 .viminfo
-rw-r--r-- 1 test test 658 3 mar 18:05 .zshrc
[t...@rhel5 ~]$ cat EOF .rpmmacros
%_topdir%(echo $HOME)/L
%_Ltopdir %{_topdir}/%{name}
%_Rtopdir %(echo $HOME)/%{name}
%_builddir %{_Ltopdir}
%_Rsourcedir%{_Rtopdir}
%_sourcedir %{_Ltopdir}
%_Rpatchdir %{_Rtopdir}
%_patchdir %{_Ltopdir}
%_Rspecdir %{_Rtopdir}
%_specdir %{_Ltopdir}
%_rpmdir%{_Ltopdir}
%_srcrpmdir %{_Ltopdir}
%_rpmfilename %%{NAME}-%%{VERSION}-%%{RELEASE}.%%{ARCH}.rpm
%_tmppath %{_topdir}/tmp
EOF
# NOTICE ALL COLLAPSE ON L/%{name} in this example
[t...@rhel5 ~]$ rpm -Uvh /tmp/iftop-0.16-4.src.rpm
Preparing...###
[100%]
1:iftop ###
[100%]
[t...@rhel5 ~]$
rpm -Uvh /tmp/iftop-0.16-4.src.rpm
Preparing...###
[100%]
1:iftop ###
[100%]
[t...@rhel5 ~]$ ls -lR L
L:
totale 8
drwxr-xr-x 2 test test 4096 3 mar 18:14 iftop
L/iftop:
totale 168
-rw-rw-r-- 1 test test 153446 8 nov 2004 iftop-0.16.tar.gz
-rw-rw-r-- 1 test test 1343 7 apr 2005 iftop.spec
[t...@esil231 ~]$ rpmbuild -ba L/iftop/iftop.spec
Esecuzione(%prep): /bin/sh -e /home/test/L/tmp/rpm-tmp.344
+ umask 022
+ cd /home/test/L/iftop
+ LANG=C
.
Regards
