Mailinglist Archive: opensuse-factory (599 mails)
| < Previous | Next > |
Re: [opensuse-factory] Running a program when launching the SUSE install part
- From: Andreas Hanke <andreas.hanke@xxxxxxxxxxxxxx>
- Date: Sun, 06 Aug 2006 15:05:00 +0200
- Message-id: <44D5E8FC.8030109@xxxxxxxxxxxxxx>
Hi,
houghi schrieb:
> Download? I have several RPMs that you could not download. Downloaded the
> source and use checkinstall to make the RPM. (I don't distribute them and
> they work for me, so don't laugh.)
houghi, these were just generic comments I made because they are
somewhat related.
What you are asking for is how to run createrepo, but what you really
want to do is installing packages from a local directory, hence my
comments about installing RPMs from a local directory in general.
> I also asume that the 'better way' is to use a repository. And that is
> just what createrepo does. It makes a repo for you. :-)
Yes and no. A repository is surely a cool thing, but should't be the
only way to install packages from a local directory.
> Concerning the bug, should I add createrepo solution to that bug, or to
> 174369? The createrepo solution is not identical to downloading an RPM and
> installing that.
createrepo is not a solution at all IMHO. Using createrepo for such a
basic functionality as installing packages from local directories
doesn't sound like a good idea to me because it means making
kdebase3-SuSE (and hence KDE) depend on a development tool (createrepo
is a development tool in my eyes).
> That could perhaps be solved by running `rpm -Uvh file.rpm`. Unfortunatly
> rpm is already linked to real, but it should not be too hard to change
> that.
>
> Or have it as a left click and run `rpm -Uvh ...rpm`. If you want it done
> by YaST, a wget to /tmp and then `yast -i /tmp/file.rpm` should sove that
> as yast can't deal with http or ftp.
/bin/rpm doesn't resolve dependencies, we are talking about installation
of local packages with depencency resolution.
Regarding your specific proposal of somehow integrating createrepo into
the YaST GUI: Well, if there is no other solution going to be in place
for 10.2, doing that might be better than not doing anything because
installing RPMs from local directories is a desperately needed feature.
But the approach looks strange. Actually I proposed it myself some time
ago, but I don't like it.
As a quick hack for now, you can create a shell script like this:
#!/bin/sh
createrepo /usr/src/packages/RPMS
/sbin/yast2 sw_single
And then change /usr/share/applications/YaST2/sw_single.desktop to have
Exec=/path/to/the/script/above
instead of
Exec=/sbin/yast2 sw_single
By the way, using a directory like /usr/src/packages/RPMS which is world
writable by default as an installation source is not secure. Consider
defining %_topdir to something else in your ~/.rpmmacros file.
Andreas Hanke
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-factory-unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory-help@xxxxxxxxxxxx
houghi schrieb:
> Download? I have several RPMs that you could not download. Downloaded the
> source and use checkinstall to make the RPM. (I don't distribute them and
> they work for me, so don't laugh.)
houghi, these were just generic comments I made because they are
somewhat related.
What you are asking for is how to run createrepo, but what you really
want to do is installing packages from a local directory, hence my
comments about installing RPMs from a local directory in general.
> I also asume that the 'better way' is to use a repository. And that is
> just what createrepo does. It makes a repo for you. :-)
Yes and no. A repository is surely a cool thing, but should't be the
only way to install packages from a local directory.
> Concerning the bug, should I add createrepo solution to that bug, or to
> 174369? The createrepo solution is not identical to downloading an RPM and
> installing that.
createrepo is not a solution at all IMHO. Using createrepo for such a
basic functionality as installing packages from local directories
doesn't sound like a good idea to me because it means making
kdebase3-SuSE (and hence KDE) depend on a development tool (createrepo
is a development tool in my eyes).
> That could perhaps be solved by running `rpm -Uvh file.rpm`. Unfortunatly
> rpm is already linked to real, but it should not be too hard to change
> that.
>
> Or have it as a left click and run `rpm -Uvh ...rpm`. If you want it done
> by YaST, a wget to /tmp and then `yast -i /tmp/file.rpm` should sove that
> as yast can't deal with http or ftp.
/bin/rpm doesn't resolve dependencies, we are talking about installation
of local packages with depencency resolution.
Regarding your specific proposal of somehow integrating createrepo into
the YaST GUI: Well, if there is no other solution going to be in place
for 10.2, doing that might be better than not doing anything because
installing RPMs from local directories is a desperately needed feature.
But the approach looks strange. Actually I proposed it myself some time
ago, but I don't like it.
As a quick hack for now, you can create a shell script like this:
#!/bin/sh
createrepo /usr/src/packages/RPMS
/sbin/yast2 sw_single
And then change /usr/share/applications/YaST2/sw_single.desktop to have
Exec=/path/to/the/script/above
instead of
Exec=/sbin/yast2 sw_single
By the way, using a directory like /usr/src/packages/RPMS which is world
writable by default as an installation source is not secure. Consider
defining %_topdir to something else in your ~/.rpmmacros file.
Andreas Hanke
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-factory-unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory-help@xxxxxxxxxxxx
| < Previous | Next > |