[opensuse-factory] checkinstall rpm not in repository
I was trying to install checkinstall but the installation kept failing. It appears the official rpms have been removed. https://software.opensuse.org/package/checkinstall?search_term=checkinstall Is there any reason why checkinstall is no longer available? I figured now would be a good time to put in place better software building and installing practices, and this would be a good place to start.
On 2017-03-08 09:21, Chan Ju Ping wrote:
I was trying to install checkinstall but the installation kept failing. It appears the official rpms have been removed.
https://software.opensuse.org/package/checkinstall?search_term=checkinstall
Is there any reason why checkinstall is no longer available? I figured now would be a good time to put in place better software building and installing practices, and this would be a good place to start.
Well, apparently the maintainers use OBS and tell everybody to use OBS, and thus neglect checkinstall to force others to also use OBS. So now I have to use "make install" directly on my systems without creating the rpm. :-( -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On Wed, 2017-03-08 at 12:50 +0100, Carlos E. R. wrote:
On 2017-03-08 09:21, Chan Ju Ping wrote:
I was trying to install checkinstall but the installation kept failing. It appears the official rpms have been removed.
https://software.opensuse.org/package/checkinstall?search_term=chec kinstall
Is there any reason why checkinstall is no longer available? I figured now would be a good time to put in place better software building and installing practices, and this would be a good place to start.
Well, apparently the maintainers use OBS and tell everybody to use OBS, and thus neglect checkinstall to force others to also use OBS.
So now I have to use "make install" directly on my systems without creating the rpm. :-(
Hello "neglect" and "force" are rather strong words, implying intention - it is nice to see that your attitude towards people behind openSUSE is still same. Regards Martin -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEwQnJ+Ps8HqIKhK3yWyRdZ/3eaFcFAli/8yoACgkQWyRdZ/3e aFdCcw/+MST1fW8H7HM5diYagslRu5CqzMq/Y0judmqW+z1tRyZs/M1GCrLCsUIg 05w1tGHh2Pn/aRdKxf0whe9JvGQ7fjA/w1ouzrTqABXKbMv6+ZEFWdXEPKKmRD5S VP/9L6ZwSfpFwZOQau7UTkHHUqWPjDUHxRrYFygbRO4EmwwB5tcuwj3Z4SOU9DDA sMS64QAsT/UM+W3/9EUq47c5zP7LqvbJrCKZiJTppY+LH5H2jSXexguyYEN76yCh mL6pgzdYKiv7U4ZjqArn/YVL8Dbv3P6OsWgUvumzde8zspLq8V8NGmOPJP1NFSG4 BjZlUV4V4Vh2BkQLLsRrG5UKQaou47d/Tj1Uo3K97nCqvp2mIRjmvwpgqv5IFioz ZEuOdFmCsDpuHjZ+RrwPijCbqbIX46lMOrtv4BAfIik4htaz7QdOMUqfmf2AD40e KhbnNTgISekWCyAxJlOZa3JmYrCB1S/RngN/RrkUuVP5gcsgg77D8FTe1IuHahCD tDYGK6scNna4czJxRBRCiZP6EftA91C7XNVZBIEeoQCPlDyIMgWGT1OsLFCXjx/k QT/NY6OvM32Am+85KBKVSxImCx2BQ7qxPmGUjpzuYN7lAJbFmq96it5VUvksUpef umpxXw7GCqd69cD+eWW4C618SwXUgJSvPoRIwkegAKNeFJX/ptY= =RlfM -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Op woensdag 8 maart 2017 12:50:20 CET schreef Carlos E. R.:
On 2017-03-08 09:21, Chan Ju Ping wrote:
I was trying to install checkinstall but the installation kept failing. It appears the official rpms have been removed.
https://software.opensuse.org/package/checkinstall?search_term=checkinstal l
Is there any reason why checkinstall is no longer available? I
figured now would be a good time to put in place better software building and installing practices, and this would be a good place to start.
Well, apparently the maintainers use OBS and tell everybody to use OBS, and thus neglect checkinstall to force others to also use OBS.
So now I have to use "make install" directly on my systems without creating the rpm. :-(
When you have a tar file with the source and you design a .spec file, which is not too difficult, on your own system, you can use rpmbuild to build a rpm. In a simple case, and I expect this to be, you can enter these two files in an OBS project to make the rpm available in a repository. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2017-03-08 13:57, Freek de Kruijf wrote:
Op woensdag 8 maart 2017 12:50:20 CET schreef Carlos E. R.:
On 2017-03-08 09:21, Chan Ju Ping wrote:
I was trying to install checkinstall but the installation kept failing. It appears the official rpms have been removed.
https://software.opensuse.org/package/checkinstall?search_term=checkinstal
l
Is there any reason why checkinstall is no longer available? I
figured now would be a good time to put in place better software building and installing practices, and this would be a good place to start.
Well, apparently the maintainers use OBS and tell everybody to use OBS, and thus neglect checkinstall to force others to also use OBS.
So now I have to use "make install" directly on my systems without creating the rpm. :-(
When you have a tar file with the source and you design a .spec file, which is not too difficult, on your own system, you can use rpmbuild to build a rpm.
Well, designing a .spec file is something I do not know how to do, it is quite difficult for me. That is precisely what checkinstall automated. Thus, rpmbuild is impossible to use, and even less OBS, wich I find terribly complex. See? You are trying to convince me to use OBS instead ;-) -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))
Op woensdag 8 maart 2017 14:04:38 CET schreef Carlos E. R.:
On 2017-03-08 13:57, Freek de Kruijf wrote:
When you have a tar file with the source and you design a .spec file, which is not too difficult, on your own system, you can use rpmbuild to build a rpm.
Well, designing a .spec file is something I do not know how to do, it is quite difficult for me. That is precisely what checkinstall automated.
Thus, rpmbuild is impossible to use, and even less OBS, wich I find terribly complex.
See? You are trying to convince me to use OBS instead ;-)
No, I am trying to convince you to put a little effort in designing a very simple .spec file. When you browse build.opensuse.org and search for a project which looks simple, you can find a simple .spec file that is an example for your .spec file. I am not much of a programmer, but understanding a simple .spec file appeared to be easy for me. rpmbuild requires a certain setup with folders to put the source and the .spec file in. Invoking rpmbuild with a few switches and the .spec file as parameters is all that is needed to get a .rpm file in this setup of folders. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed 08 Mar 2017 02:27:33 PM CST, Freek de Kruijf wrote:
No, I am trying to convince you to put a little effort in designing a very simple .spec file. When you browse build.opensuse.org and search for a project which looks simple, you can find a simple .spec file that is an example for your .spec file. I am not much of a programmer, but understanding a simple .spec file appeared to be easy for me. rpmbuild requires a certain setup with folders to put the source and the .spec file in. Invoking rpmbuild with a few switches and the .spec file as parameters is all that is needed to get a .rpm file in this setup of folders.
Hi No need to even design, it's already available; vi test.spec Or whatever the package is called. Plus when using OBS (or osc locally) , far better checks (rpmlint) on the end product to ensure it's really fit for use.... -- Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890) openSUSE Leap 42.1|GNOME 3.16.2|4.1.36-44-default up 3 days 11:54, 4 users, load average: 0.64, 0.32, 0.35 CPU AMD Athlon(tm) II X4 635 @ 2.90GHz | GPU Nvidia GeForce 8800 GT -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2017-03-08 14:27, Freek de Kruijf wrote:
Op woensdag 8 maart 2017 14:04:38 CET schreef Carlos E. R.:
On 2017-03-08 13:57, Freek de Kruijf wrote:
When you have a tar file with the source and you design a .spec file, which is not too difficult, on your own system, you can use rpmbuild to build a rpm.
Well, designing a .spec file is something I do not know how to do, it is quite difficult for me. That is precisely what checkinstall automated.
Thus, rpmbuild is impossible to use, and even less OBS, wich I find terribly complex.
See? You are trying to convince me to use OBS instead ;-)
No, I am trying to convince you to put a little effort in designing a very simple .spec file. When you browse build.opensuse.org and search for a project which looks simple, you can find a simple .spec file that is an example for your .spec file. I am not much of a programmer, but understanding a simple .spec file appeared to be easy for me. rpmbuild requires a certain setup with folders to put the source and the .spec file in. Invoking rpmbuild with a few switches and the .spec file as parameters is all that is needed to get a .rpm file in this setup of folders.
Again, you are trying to convince me to not use checkinstall, see? :-) I have been told for about two decades to not use checkinstall. To do more or less what you describe. What you do not understand is that *creating* an spec file is not something I can do. How do you expect me to know what files to put inside? I have no idea. There are tars that do contain an spec file, but it is designed for another distribution. And you expect me to learn and find out how to do that conversion! Even on a complex build, checkinstall created automatically that spec file, no thinking at all needed. Instead of making checkinstall available on the distro, you all are telling me to use tools that I find too difficult to use, to use procedures that I find way too difficult to follow, and forget checkinstall. Exactly what I said you do. Well, no, I'm incapable of learning that skill. Call me stupid if you wish. - -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAljAS1EACgkQja8UbcUWM1zUVQEAiLHLAhm84fzAobq4lAHsFGZF qA1F/EKKHHOEiS4kQFoA/06mDvy9tytOXcPHRFwNTnBceHEA2/8xxIRFCfbGgyiF =YAFc -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
2017-03-08 15:20 GMT-03:00 Carlos E. R.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2017-03-08 14:27, Freek de Kruijf wrote:
Op woensdag 8 maart 2017 14:04:38 CET schreef Carlos E. R.:
On 2017-03-08 13:57, Freek de Kruijf wrote:
When you have a tar file with the source and you design a .spec file, which is not too difficult, on your own system, you can use rpmbuild to build a rpm.
Well, designing a .spec file is something I do not know how to do, it is quite difficult for me. That is precisely what checkinstall automated.
Thus, rpmbuild is impossible to use, and even less OBS, wich I find terribly complex.
See? You are trying to convince me to use OBS instead ;-)
No, I am trying to convince you to put a little effort in designing a very simple .spec file. When you browse build.opensuse.org and search for a project which looks simple, you can find a simple .spec file that is an example for your .spec file. I am not much of a programmer, but understanding a simple .spec file appeared to be easy for me. rpmbuild requires a certain setup with folders to put the source and the .spec file in. Invoking rpmbuild with a few switches and the .spec file as parameters is all that is needed to get a .rpm file in this setup of folders.
Again, you are trying to convince me to not use checkinstall, see? :-)
I have been told for about two decades to not use checkinstall. To do more or less what you describe. What you do not understand is that *creating* an spec file is not something I can do. How do you expect me to know what files to put inside? I have no idea.
There are tars that do contain an spec file, but it is designed for another distribution. And you expect me to learn and find out how to do that conversion!
Even on a complex build, checkinstall created automatically that spec file, no thinking at all needed.
Instead of making checkinstall available on the distro, you all are telling me to use tools that I find too difficult to use, to use procedures that I find way too difficult to follow, and forget checkinstall. Exactly what I said you do.
Well, no, I'm incapable of learning that skill. Call me stupid if you wish.
- -- Cheers / Saludos,
Carlos E. R.
Hi, I'm wondering whats the difficult in create a .spec file, especially the part of don't know where to put files. Just do it whitout the %files, it will display the files that are not owned, so you put this files in %files sections... Even a noob like me (no knowledge on any programming language, incapable of create a single script) can do some packaging in OBS Regards, Luiz -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2017-03-08 19:31, Luiz Fernando Ranghetti wrote:
Hi,
I'm wondering whats the difficult in create a .spec file, especially the part of don't know where to put files. Just do it whitout the %files, it will display the files that are not owned, so you put this files in %files sections...
What will display that list?
Even a noob like me (no knowledge on any programming language, incapable of create a single script) can do some packaging in OBS
Well, I do write scripts, and programs. I can't create specs. I see lists of files. I see defines. I see macros. I see... No, it is bewildering. :-( - -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAljAT+wACgkQja8UbcUWM1xfHgD+JGUt2SRQEkW1953q2IddApXp oTimWD/YPD7DgmGJAmYA+gNsPb5kCbG0LMD4IQd7jaWXvHOwJ9+E/hv4rh/wEEdI =xhIC -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wednesday 2017-03-08 19:39, Carlos E. R. wrote:
I'm wondering whats the difficult in create a .spec file, especially the part of don't know where to put files. Just do it whitout the %files, it will display the files that are not owned, so you put this files in %files sections...
What will display that list?
Like he said, an empty %files list will cause rpm to emit a list of files that are yet to be checked. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
2017-03-08 16:14 GMT-03:00 Jan Engelhardt
On Wednesday 2017-03-08 19:39, Carlos E. R. wrote:
I'm wondering whats the difficult in create a .spec file, especially the part of don't know where to put files. Just do it whitout the %files, it will display the files that are not owned, so you put this files in %files sections...
What will display that list?
Like he said, an empty %files list will cause rpm to emit a list of files that are yet to be checked. --
Like this: https://build.opensuse.org/package/live_build_log/home:elchevive/hello/openS... for this spec (I commented the files on %files sections and %lang_package to produce the error) https://build.opensuse.org/package/view_file/home:elchevive/hello/hello.spec... the spec run: make, make check and make install, nothing more Regards Luiz -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, Mar 8, 2017 at 1:39 PM, Carlos E. R.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2017-03-08 19:31, Luiz Fernando Ranghetti wrote:
Hi,
I'm wondering whats the difficult in create a .spec file, especially the part of don't know where to put files. Just do it whitout the %files, it will display the files that are not owned, so you put this files in %files sections...
What will display that list?
Even a noob like me (no knowledge on any programming language, incapable of create a single script) can do some packaging in OBS
Well, I do write scripts, and programs. I can't create specs.
I see lists of files. I see defines. I see macros. I see... No, it is bewildering. :-(
Carlos, At least take 10 minutes and see what it's like: 1) Use you bugzilla credential to log into https://build.opensuse.org/ (that does some one time setup stuff the first time). 2) Install osc (zypper in osc) 3) Create a new working directory tree area to work in. I use ~/obs mkdir ~/obs; cd ~obs 4) Check-out a package from OBS. This will get dc3dd from Leap 42.1 osc co openSUSE:Leap:42.1:Update dc3dd 5) Hop into the directory that now has the files needed to do a local build. cd i~/obs/openSUSE:Leap:42.1:Update/dc3dd 6) Confirm you can do a local build (--local is needed for this because the tarball is no longer on line where it was) osc build --local That causes a chroot jail to be built with a new set of RPMs downloaded from OBS. Inside the jail the build pre-reqs are installed and the build performed. The last few lines of the above tell you where to find the RPMs. You can install the RPMs or copy them to some local repo if you like. 7) Scream and shout that you have built your first set of RPMs via the OBS/osc mechanism 8) Break the spec file by deleting the lines immediately following %files near the end of the spec file vi *.spec (and comment out these 4 lines from the %files section # %doc ChangeLog COPYING NEWS THANKS # %doc *.txt # %{_bindir}/dc3dd # %{_mandir}/man1/dc3dd.1%{ext_man} 9) Try to build again, but note that you get errors at the end of the output: osc build --local [ 39s] Checking for unpackaged file(s): /usr/lib/rpm/check-files /home/abuild/rpmbuild/BUILDROOT/dc3dd-7.2.0-0.x86_64 [ 39s] error: Installed (but unpackaged) file(s) found: [ 39s] /usr/bin/dc3dd [ 39s] /usr/lib/debug/.build-id/1b/4095a17a0d90380f46f99d989398e0f8d95563 [ 39s] /usr/lib/debug/.build-id/1b/4095a17a0d90380f46f99d989398e0f8d95563.debug [ 39s] /usr/lib/debug/usr/bin/dc3dd.debug [ 39s] /usr/share/man/man1/dc3dd.1.gz [ 39s] [ 39s] [ 39s] RPM build errors: [ 39s] Installed (but unpackaged) file(s) found: [ 39s] /usr/bin/dc3dd [ 39s] /usr/lib/debug/.build-id/1b/4095a17a0d90380f46f99d989398e0f8d95563 [ 39s] /usr/lib/debug/.build-id/1b/4095a17a0d90380f46f99d989398e0f8d95563.debug [ 39s] /usr/lib/debug/usr/bin/dc3dd.debug [ 39s] /usr/share/man/man1/dc3dd.1.gz [ 39s] [ 39s] Thermaltake failed "build dc3dd.spec" at Wed Mar 8 19:19:29 UTC 2017. [ 39s] 10) Now the actual tricky part Note that several of the unpackaged files are debug files. Ignore them. Look at the files you don't have included and at the lines you commented out. Note the correlation and uncomment these two: %{_bindir}/dc3dd %{_mandir}/man1/dc3dd.1%{ext_man} 11) Try the build again osc build --local Success again! 12) Compare what you have with what's in OBS osc diff %files %defattr(-,root,root) -%doc ChangeLog COPYING NEWS THANKS -%doc *.txt +# %doc ChangeLog COPYING NEWS THANKS +# %doc *.txt %{_bindir}/dc3dd %{_mandir}/man1/dc3dd.1%{ext_man} So you're removed the inclusion of some doc files, but at least for building, that didn't break anything. If you tried to issue an SR to do that, you would get blocked. Either by automation or a juman review. 12) Restore you spec file to virgin rm dc3dd.spec osc up ============ And that's the first basics, Admittedly there is a lot more to learn, but it is doable and the ability to checkout working packages as a reference really simplifies the learning curve. Greg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thursday, 9 March 2017 03:35:57 MYT Greg Freemyer wrote:
At least take 10 minutes and see what it's like:
1) Use you bugzilla credential to log into https://build.opensuse.org/ (that does some one time setup stuff the first time).
2) Install osc (zypper in osc)
3) Create a new working directory tree area to work in. I use ~/obs
mkdir ~/obs; cd ~obs
4) Check-out a package from OBS. This will get dc3dd from Leap 42.1
osc co openSUSE:Leap:42.1:Update dc3dd
5) Hop into the directory that now has the files needed to do a local build.
cd i~/obs/openSUSE:Leap:42.1:Update/dc3dd
6) Confirm you can do a local build (--local is needed for this because the tarball is no longer on line where it was)
osc build --local
That causes a chroot jail to be built with a new set of RPMs downloaded from OBS. Inside the jail the build pre-reqs are installed and the build performed.
The last few lines of the above tell you where to find the RPMs. You can install the RPMs or copy them to some local repo if you like.
7) Scream and shout that you have built your first set of RPMs via the OBS/osc mechanism
8) Break the spec file by deleting the lines immediately following %files near the end of the spec file
vi *.spec (and comment out these 4 lines from the %files section
# %doc ChangeLog COPYING NEWS THANKS # %doc *.txt # %{_bindir}/dc3dd # %{_mandir}/man1/dc3dd.1%{ext_man}
9) Try to build again, but note that you get errors at the end of the
Thanks for the clearly written tutorial. I will learn to do it this way instead.
output:
osc build --local
[ 39s] Checking for unpackaged file(s): /usr/lib/rpm/check-files /home/abuild/rpmbuild/BUILDROOT/dc3dd-7.2.0-0.x86_64 [ 39s] error: Installed (but unpackaged) file(s) found: [ 39s] /usr/bin/dc3dd [ 39s] /usr/lib/debug/.build-id/1b/4095a17a0d90380f46f99d989398e0f8d95563 [ 39s] /usr/lib/debug/.build-id/1b/4095a17a0d90380f46f99d989398e0f8d95563.debug [ 39s] /usr/lib/debug/usr/bin/dc3dd.debug [ 39s] /usr/share/man/man1/dc3dd.1.gz [ 39s] [ 39s] [ 39s] RPM build errors: [ 39s] Installed (but unpackaged) file(s) found: [ 39s] /usr/bin/dc3dd [ 39s] /usr/lib/debug/.build-id/1b/4095a17a0d90380f46f99d989398e0f8d95563 [ 39s] /usr/lib/debug/.build-id/1b/4095a17a0d90380f46f99d989398e0f8d95563.debug [ 39s] /usr/lib/debug/usr/bin/dc3dd.debug [ 39s] /usr/share/man/man1/dc3dd.1.gz [ 39s] [ 39s] Thermaltake failed "build dc3dd.spec" at Wed Mar 8 19:19:29 UTC 2017. [ 39s]
10) Now the actual tricky part
Note that several of the unpackaged files are debug files. Ignore them.
Look at the files you don't have included and at the lines you commented out. Note the correlation and uncomment these two:
%{_bindir}/dc3dd %{_mandir}/man1/dc3dd.1%{ext_man}
11) Try the build again
osc build --local
Success again!
12) Compare what you have with what's in OBS
osc diff
%files %defattr(-,root,root) -%doc ChangeLog COPYING NEWS THANKS -%doc *.txt +# %doc ChangeLog COPYING NEWS THANKS +# %doc *.txt %{_bindir}/dc3dd %{_mandir}/man1/dc3dd.1%{ext_man}
So you're removed the inclusion of some doc files, but at least for building, that didn't break anything. If you tried to issue an SR to do that, you would get blocked. Either by automation or a juman review.
12) Restore you spec file to virgin
rm dc3dd.spec osc up
============
And that's the first basics, Admittedly there is a lot more to learn, but it is doable and the ability to checkout working packages as a reference really simplifies the learning curve.
Greg
On Thu, Mar 9, 2017 at 12:08 AM, Chan Ju Ping
On Thursday, 9 March 2017 03:35:57 MYT Greg Freemyer wrote:
At least take 10 minutes and see what it's like:
1) Use you bugzilla credential to log into https://build.opensuse.org/ (that does some one time setup stuff the first time).
2) Install osc (zypper in osc)
3) Create a new working directory tree area to work in. I use ~/obs
mkdir ~/obs; cd ~obs
4) Check-out a package from OBS. This will get dc3dd from Leap 42.1
osc co openSUSE:Leap:42.1:Update dc3dd
5) Hop into the directory that now has the files needed to do a local build.
cd i~/obs/openSUSE:Leap:42.1:Update/dc3dd
6) Confirm you can do a local build (--local is needed for this because the tarball is no longer on line where it was)
osc build --local
That causes a chroot jail to be built with a new set of RPMs downloaded from OBS. Inside the jail the build pre-reqs are installed and the build performed.
The last few lines of the above tell you where to find the RPMs. You can install the RPMs or copy them to some local repo if you like.
7) Scream and shout that you have built your first set of RPMs via the OBS/osc mechanism
8) Break the spec file by deleting the lines immediately following %files near the end of the spec file
vi *.spec (and comment out these 4 lines from the %files section
# %doc ChangeLog COPYING NEWS THANKS # %doc *.txt # %{_bindir}/dc3dd # %{_mandir}/man1/dc3dd.1%{ext_man}
9) Try to build again, but note that you get errors at the end of the
Thanks for the clearly written tutorial. I will learn to do it this way instead.
Chan, We have a mailing list dedicated to helping people do it this way. opensuse-packaging Every package in openSUSE uses this OBS/osc combination to be built for the release. I believe openSUSE has several key enabling technologies, but OBS/osc is one of the most important. If you want to understand how openSUSE is built, you have to understand OBS/osc. I personally use the osc mechanism for most of my builds, and the OBS WebUI for most of my package maintenance that doesn't include modifying the files in a package. ie. most *.spec, *.changes, *.patch changes are done on my PC first. Choosing repos to build for, sending SRs, branching packages, I typically do via the WebUI. Thus when working on a package I tend to have both a konsole window open and a browser window open to OBS for the WebUI. Anyway, come over to -packaging and ask your questions. Learning to use OBS/osc is not a topic for -factory. Greg -- Greg Freemyer -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2017-03-08 20:35, Greg Freemyer wrote:
On Wed, Mar 8, 2017 at 1:39 PM, Carlos E. R. <> wrote:
Carlos,
At least take 10 minutes and see what it's like:
I have an OBS account, I dedicated hours to try. Not good. Compare your write up with: ./configure make su checkinstall Done. Anyway, thanks for your write work, I will try again.
1) Use you bugzilla credential to log into https://build.opensuse.org/ (that does some one time setup stuff the first time).
2) Install osc (zypper in osc)
3) Create a new working directory tree area to work in. I use ~/obs
mkdir ~/obs; cd ~obs
4) Check-out a package from OBS. This will get dc3dd from Leap 42.1
This assumes that it already exists. If I want to go this way is to build something that does not exist.
osc co openSUSE:Leap:42.1:Update dc3dd
5) Hop into the directory that now has the files needed to do a local build.
cd i~/obs/openSUSE:Leap:42.1:Update/dc3dd
6) Confirm you can do a local build (--local is needed for this because the tarball is no longer on line where it was)
osc build --local
That causes a chroot jail to be built with a new set of RPMs downloaded from OBS. Inside the jail the build pre-reqs are installed and the build performed.
The last few lines of the above tell you where to find the RPMs. You can install the RPMs or copy them to some local repo if you like.
7) Scream and shout that you have built your first set of RPMs via the OBS/osc mechanism
8) Break the spec file by deleting the lines immediately following %files near the end of the spec file
vi *.spec (and comment out these 4 lines from the %files section
# %doc ChangeLog COPYING NEWS THANKS # %doc *.txt # %{_bindir}/dc3dd # %{_mandir}/man1/dc3dd.1%{ext_man}
9) Try to build again, but note that you get errors at the end of the output:
osc build --local
[ 39s] Checking for unpackaged file(s): /usr/lib/rpm/check-files /home/abuild/rpmbuild/BUILDROOT/dc3dd-7.2.0-0.x86_64 [ 39s] error: Installed (but unpackaged) file(s) found: [ 39s] /usr/bin/dc3dd [ 39s] /usr/lib/debug/.build-id/1b/4095a17a0d90380f46f99d989398e0f8d95563 [ 39s] /usr/lib/debug/.build-id/1b/4095a17a0d90380f46f99d989398e0f8d95563.debug
[ 39s] /usr/lib/debug/usr/bin/dc3dd.debug
[ 39s] /usr/share/man/man1/dc3dd.1.gz [ 39s] [ 39s] [ 39s] RPM build errors: [ 39s] Installed (but unpackaged) file(s) found: [ 39s] /usr/bin/dc3dd [ 39s] /usr/lib/debug/.build-id/1b/4095a17a0d90380f46f99d989398e0f8d95563 [ 39s] /usr/lib/debug/.build-id/1b/4095a17a0d90380f46f99d989398e0f8d95563.debug
[ 39s] /usr/lib/debug/usr/bin/dc3dd.debug
[ 39s] /usr/share/man/man1/dc3dd.1.gz [ 39s] [ 39s] Thermaltake failed "build dc3dd.spec" at Wed Mar 8 19:19:29 UTC 2017. [ 39s]
10) Now the actual tricky part
Note that several of the unpackaged files are debug files. Ignore them.
Look at the files you don't have included and at the lines you commented out. Note the correlation and uncomment these two:
%{_bindir}/dc3dd %{_mandir}/man1/dc3dd.1%{ext_man}
11) Try the build again
osc build --local
Success again!
12) Compare what you have with what's in OBS
osc diff
%files %defattr(-,root,root) -%doc ChangeLog COPYING NEWS THANKS -%doc *.txt +# %doc ChangeLog COPYING NEWS THANKS +# %doc *.txt %{_bindir}/dc3dd %{_mandir}/man1/dc3dd.1%{ext_man}
So you're removed the inclusion of some doc files, but at least for building, that didn't break anything. If you tried to issue an SR to do that, you would get blocked. Either by automation or a juman review.
12) Restore you spec file to virgin
rm dc3dd.spec osc up
============
And that's the first basics, Admittedly there is a lot more to learn, but it is doable and the ability to checkout working packages as a reference really simplifies the learning curve.
I'll try, but you are departing from an already existing and correct .spec file. On what I may want to build, there will not be at all a spec, or it exists for ubuntu or debian or something else with different standards. Thanks. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))
On Fri, Mar 10, 2017 at 10:01 AM, Carlos E. R.
On 2017-03-08 20:35, Greg Freemyer wrote:
On Wed, Mar 8, 2017 at 1:39 PM, Carlos E. R. <> wrote:
Carlos,
At least take 10 minutes and see what it's like:
I have an OBS account, I dedicated hours to try. Not good.
Compare your write up with:
./configure make su checkinstall
Done.
I imagine a very simple specfile base could be created with similar funtionality, but I don't actually know what all checkinstall does.
Anyway, thanks for your write work, I will try again.
1) Use you bugzilla credential to log into https://build.opensuse.org/ (that does some one time setup stuff the first time).
2) Install osc (zypper in osc)
3) Create a new working directory tree area to work in. I use ~/obs
mkdir ~/obs; cd ~obs
4) Check-out a package from OBS. This will get dc3dd from Leap 42.1
This assumes that it already exists. If I want to go this way is to build something that does not exist.
I rarely create a specfile from scratch. It can be done, but in my opinion it is not a good way to start/learn. I find packages with similar structure to what I need, then make a copy of it and turn it into the package I want. <big snip>
============
And that's the first basics, Admittedly there is a lot more to learn, but it is doable and the ability to checkout working packages as a reference really simplifies the learning curve.
I'll try, but you are departing from an already existing and correct .spec file. On what I may want to build, there will not be at all a spec, or it exists for ubuntu or debian or something else with different standards.
I rarely come across things that aren't in OBS at all. It maybe a non-compiling version, or more likely an out-of-date version. I copy the package to my home project, then fix build issues (if any), then update to latest release from upstream, then review the specfile for improvements. I normally then SR the package to a devel project, or even to factory. Getting checkinstall checked out to your PC and and RPM built seems not to hard based on someone else's email. Give it a shot and keep it in your own home project at a minimum. If you get comfortable enough, SR it to a devel project. If you really want to see it in the distro, SR it to factory. And from factory to Leap 42.3 Greg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wednesday, 8 March 2017 19:20 Carlos E. R. wrote:
Again, you are trying to convince me to not use checkinstall, see? :-)
I have been told for about two decades to not use checkinstall. To do more or less what you describe. What you do not understand is that *creating* an spec file is not something I can do. How do you expect me to know what files to put inside? I have no idea.
It's always very sad for me to see someone with this attitude. Were you always like this? Like "reading is not something I can do"? Doesn't seem so as you apparently can read now and I seriously doubt you could read when you were born.
There are tars that do contain an spec file, but it is designed for another distribution. And you expect me to learn and find out how to do that conversion!
Obviously. It's really that simple: either there is someone else who is both able and willing to do the job or you have to decide, either you learn how to do it or you won't have the package. People can learn things. Those who can write specfiles were not born with the skill, they had to learn it at some moment.
Even on a complex build, checkinstall created automatically that spec file, no thinking at all needed.
Just an idea... If you are willing to do "make install" rather than learn about specfiles, did you consider installing just checkinstall itself this way and then use it on other software? Including itself, if possible - if it's as powerful and flawless as you say, it should be able to package itself.
Instead of making checkinstall available on the distro, you all are telling me to use tools that I find too difficult to use, to use procedures that I find way too difficult to follow, and forget checkinstall. Exactly what I said you do.
Wanting something doesn't make it happen, world doesn't work like that. Some packages in openSUSE come from SLE (or are maintained to be forked for SLE one day) but checkinstall is not one of them (no surprise). Thus it's only going to be available if there is someone who is willing to package it and maintain it. Or just the latter if the package already exists - which is most likely the case here, you can copy it from last openSUSE version where it was. If there isn't such person, package doesn't get into openSUSE. Good old Mr. Someone Else is not obliged to do it for you.
Well, no, I'm incapable of learning that skill.
Are you sure? Did you seriously try? I mean really try, not just open a specfile and say "no, it's too complicated"? Like investing few hours into googling for some tutorials on the topic and reading them? It's really hard for me to believe there is someone who can write shell scripts but is _unable_ to learn how to write a specfile. I have experience with both and trust me, scripting in shell is way harder than writing specfiles (except for the part where you often need to write some shell scriptlet in the specfile). Unwilling, that's a different story. Understand, I find perfectly acceptable if someone decides he's not willing to spend the few hours needed to learn how to write specfiles; I have a lot of topics myself that I could learn if I decided to but I didn't for whatever reason. What I find wrong is if someone insists that someone else has to do what he doesn't want to (for whatever reason).
Call me stupid if you wish.
To be honest, "stupid" wasn't actually the first word that came to my mind when I read your e-mail(s). It was "lazy" ("demanding" was second). It may sound harsh but that's what my immediate reaction was. Michal Kubeček -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi,
On Thu, Mar 9, 2017 at 9:15 AM, Michal Kubecek
Unwilling, that's a different story. Understand, I find perfectly acceptable if someone decides he's not willing to spend the few hours needed to learn how to write specfiles; I have a lot of topics myself that I could learn if I decided to but I didn't for whatever reason. What I find wrong is if someone insists that someone else has to do what he doesn't want to (for whatever reason).
Call me stupid if you wish.
To be honest, "stupid" wasn't actually the first word that came to my mind when I read your e-mail(s). It was "lazy" ("demanding" was second). It may sound harsh but that's what my immediate reaction was.
I'm mostly with Carlos on this. Yes, users should learn new things, when they have time, but as a professional SW developer from 1978 I "learned" that it is very important that developers learn how the users are using their products and try helping them. It should be two-way, not to just force users to go the way developers prefer (Microsoft way - when BG or whoever decided what is best for everybody). I do like what Ludwig wrote, it seems a better approach. Carlos, I tried to use osc as Greg described and checked out the checkinstall from one of the user projects (home:adra). It worked fine (well, it also installed some stuff I do not need, like mercury). So I've built checkinstall RPM and installed it on my Tumbleweeds system. It was really straightforward. BR, -- Mark Goldstein -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thu, Mar 09, 2017 at 06:24:26PM +0200, Mark Goldstein wrote:
I'm mostly with Carlos on this. Yes, users should learn new things, when they have time, but as a professional SW developer from 1978 I "learned" that it is very important that developers learn how the users are using their products and try helping them. It should be two-way, not to just force users to go the way developers prefer (Microsoft way - when BG or whoever decided what is best for everybody).
This is different. Developer ignoring what users actually do and preferring his own visions (gimp "save" vs. "export" flame comes to my mind as a nice example) is not what happened here. As someone already explained, the reason for checkinstall being removed was _not_ some "elders" deciding it will be kicked out in order to force users to do things "the right way". No, the reason was the package was literally broken and there was literally nobody willing to fix it and take over its maintainership. Users wanting to use checkinstall do not make a maintainer materialize out of thin air. If we were talking about SLE, it would be possible that managers would decide certain package is so important for the product that they would make sure someone does maintain it. But openSUSE doesn't work like this, in openSUSE if a package doesn't motivate anyone to maintain it, it's not in the distribution, no matter how many users would like to see it there. An orphaned package may stay in the distribution for some time, as long as there are people who are willing to do simple fixes to cope with e.g. new and stricter OBS checks; but in the long term, only a dedicated maintainer is the way to keep a package in the distribution. So if Carlos or anyone else really wants checkinstall in openSUSE, I can see only two options for them: (a) grind their teeth, learn how to do packaging and prepare an acceptable package (if they just want an RPM, not necessarily in the distribution, replace "acceptable" by "working") or (b) convince someone else to do the job for them. If Carlos' e-mails in this thread were an attempt for (b), it's IMHO unlikely to work.
I do like what Ludwig wrote, it seems a better approach.
Carlos, I tried to use osc as Greg described and checked out the checkinstall from one of the user projects (home:adra). It worked fine (well, it also installed some stuff I do not need, like mercury). So I've built checkinstall RPM and installed it on my Tumbleweeds system. It was really straightforward.
This is a quote from my e-mail you responded to:
Thus it's only going to be available if there is someone who is willing to package it and maintain it. Or just the latter if the package already exists - which is most likely the case here, you can copy it from last openSUSE version where it was.
Does it really differ that much? I just suggested last known working version from the distribution rather than random home project. Michal Kubeček -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 09.03.2017 21:12, Michal Kubecek wrote:
Users wanting to use checkinstall do not make a maintainer materialize out of thin air. If we were talking about SLE, it would be possible that managers would decide certain package is so important for the product that they would make sure someone does maintain it. But openSUSE doesn't work like this, in openSUSE if a package doesn't motivate anyone to maintain it, it's not in the distribution, no matter how many users would like to see it there.
Well, I actually sometimes look into packages on the "wish list" of many users (in other words: often mentioned in threads like this) and think about maintaining them, even though I do not really need or use them, just to do some users a favor. One example are the lots of XFCE parts that I do not personally use (almost all panel plugins and stuff like file managers etc), but where I know that users exist and where I receive occasional bugreports. But to be honest: this is also because those users / bugreporters are most of the time very nice and friendly people, who do what they can to help.
So if Carlos or anyone else really wants checkinstall in openSUSE, I can see only two options for them: (a) grind their teeth, learn how to do packaging and prepare an acceptable package (if they just want an RPM, not necessarily in the distribution, replace "acceptable" by "working") or (b) convince someone else to do the job for them. If Carlos' e-mails in this thread were an attempt for (b), it's IMHO unlikely to work.
Exactly. I would not touch checkinstall with a five foot pole, because from this thread, I can already assume what curses I would receive, would I decide a few years from now, that I don't want to maintain it anymore... :-)
Does it really differ that much? I just suggested last known working version from the distribution rather than random home project.
Well, this random home project is actually a few patches ahead of the "last known not working version" (it was dropped supposedly because it did *not* work) and looks like it is fixed and (sort of) maintained. -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thu, Mar 9, 2017 at 10:12 PM, Michal Kubecek
This is a quote from my e-mail you responded to:
Thus it's only going to be available if there is someone who is willing to package it and maintain it. Or just the latter if the package already exists - which is most likely the case here, you can copy it from last openSUSE version where it was.
Does it really differ that much? I just suggested last known working version from the distribution rather than random home project.
Michal, I have to apologize. I did not read your mail carefully enough. What you said is quite reasonable. I just felt that Ludwig was kind of "more gentle" to the user habits. I have not used checkinstall for quite some time, but when I did (as Carlos also mentioned), there were many warnings that it is broken, even dangerous. Still it worked well for me and I was able to create RPMs from some stuff that was not provided by openSUSE (or openSUSE version did not work for me). (IIRC it was related to old PocketPC support packages, working through USB, there were some patches to kernel drivers to apply. It was related to specific chipsets). So my feeling then was like it is too early to discard this simple tool. Regards, -- Mark Goldstein -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Op woensdag 8 maart 2017 14:04:38 CET schreef Carlos E. R.:
On 2017-03-08 13:57, Freek de Kruijf wrote:
Op woensdag 8 maart 2017 12:50:20 CET schreef Carlos E. R.:
On 2017-03-08 09:21, Chan Ju Ping wrote:
I was trying to install checkinstall but the installation kept failing. It appears the official rpms have been removed.
https://software.opensuse.org/package/checkinstall?search_term=checkinst al
l
Is there any reason why checkinstall is no longer available? I
figured now would be a good time to put in place better software building and installing practices, and this would be a good place to start.
Well, apparently the maintainers use OBS and tell everybody to use OBS, and thus neglect checkinstall to force others to also use OBS.
So now I have to use "make install" directly on my systems without creating the rpm. :-(
When you have a tar file with the source and you design a .spec file, which is not too difficult, on your own system, you can use rpmbuild to build a rpm.
Well, designing a .spec file is something I do not know how to do, it is quite difficult for me. That is precisely what checkinstall automated.
Thus, rpmbuild is impossible to use, and even less OBS, wich I find terribly complex.
See? You are trying to convince me to use OBS instead ;-)
I consider this "refusal to learn". The appropriate URLs should be in your mail dozens of times. And, if you quote, do not leave out essential parts. This is what Freek wrote: "When you have a tar file with the source and you design a .spec file, which is not too difficult, on your own system, you can use rpmbuild to build a rpm. In a simple case, and I expect this to be, you can enter these two files in an OBS project to make the rpm available in a repository." -- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Op woensdag 8 maart 2017 12:50:20 CET schreef Carlos E. R.:
On 2017-03-08 09:21, Chan Ju Ping wrote:
I was trying to install checkinstall but the installation kept failing. It appears the official rpms have been removed.
https://software.opensuse.org/package/checkinstall?search_term=checkinstal l
Is there any reason why checkinstall is no longer available? I
figured now would be a good time to put in place better software building and installing practices, and this would be a good place to start.
Well, apparently the maintainers use OBS and tell everybody to use OBS, and thus neglect checkinstall to force others to also use OBS.
So now I have to use "make install" directly on my systems without creating the rpm. :-(
Then use 10% of the time you spend making insinuations like 'neglect', 'force', having these endless right/wrong debates to get your hands on OBS. You could become a top contributor. -- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Carlos E. R. wrote:
On 2017-03-08 09:21, Chan Ju Ping wrote:
I was trying to install checkinstall but the installation kept failing. It appears the official rpms have been removed.
https://software.opensuse.org/package/checkinstall?search_term=checkinstall
Is there any reason why checkinstall is no longer available? I figured now would be a good time to put in place better software building and installing practices, and this would be a good place to start.
Well, apparently the maintainers use OBS and tell everybody to use OBS, and thus neglect checkinstall to force others to also use OBS.
Carlos, the "problem" with checkinstall is that it is a beginner's tool. IMO it's natural that people to outgrow it and then lose interest. checkinstall wasn't dropped in order to force anyone into OBS. The delete message rather indicates that it was unmaintained both on opensuse as well as upstream side. It probably didn't build anymore. It is a beginner's tool because it only tracks the actual installation. It doesn't help to make the compilation reproducible. As soon as one has to update a package regularly, that's exactly what's needed though. One year later nobody remembers what configure switches were used originally. So that's where spec files and rpmbuild help with. Easy to produce updated packages that way. Finally, as soon as one has to maintain several packages, that probably even depend on each other or need to be built for different distros, OBS comes into play. Clean package builds, fully automated! Real pros go the extra mile after that and submit their packages for inclusion into the distribution of course :-) At this level checkinstall is of limited use then. Nevertheless it has it's right to exist for beginners and sometimes also if one doesn't care about "doing it the right way" IMO. Better than plain "make install" that circumvents package management completely for sure. So Carlos and Chan, if checkinstall is important to you, you are predestined to take care of it and make sure it works in openSUSE. There are still some instances of it made by other users in OBS. So the spec file for it is already written :-) Maybe you can team up with them to get checkinstall into Factory again and from there to the stable releases. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2017-03-09 10:58, Ludwig Nussel wrote:
Carlos E. R. wrote:
Carlos, the "problem" with checkinstall is that it is a beginner's tool. IMO it's natural that people to outgrow it and then lose interest. checkinstall wasn't dropped in order to force anyone into OBS. The delete message rather indicates that it was unmaintained both on opensuse as well as upstream side. It probably didn't build anymore.
Yes, I am aware that it is a beginners tool. I'm not a pro.
It is a beginner's tool because it only tracks the actual installation. It doesn't help to make the compilation reproducible. As soon as one has to update a package regularly, that's exactly what's needed though. One year later nobody remembers what configure switches were used originally. So that's where spec files and rpmbuild help with. Easy to produce updated packages that way.
Finally, as soon as one has to maintain several packages, that probably even depend on each other or need to be built for different distros, OBS comes into play. Clean package builds, fully automated!
But that's not the common user case.
Real pros go the extra mile after that and submit their packages for inclusion into the distribution of course :-)
But I'm not a pro...
At this level checkinstall is of limited use then. Nevertheless it has it's right to exist for beginners and sometimes also if one doesn't care about "doing it the right way" IMO. Better than plain "make install" that circumvents package management completely for sure.
Which is what I am indeed using, plain make install.
So Carlos and Chan, if checkinstall is important to you, you are predestined to take care of it and make sure it works in openSUSE. There are still some instances of it made by other users in OBS. So the spec file for it is already written :-) Maybe you can team up with them to get checkinstall into Factory again and from there to the stable releases.
I will indeed try to find out if I can build checkinstall for myself, yes. Thanks for the hints. But no, I will not provide it for others in OBS, I'm not a pro. I can't take that responsibility. And yes, I do have an OBS account, and I have dedicated hours to reading documents and trying. Not minutes as some here hinted. Didn't work out :-( - -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAljCw5IACgkQja8UbcUWM1wsFAD+KMkHeMUcDxN96vNkUMJXuzCZ n4Ox73FyVqGf3azsXfMA/jIhVidTw1oj3qR+VJOts4bAwt4HnFRDcyLrZ3tLvpAN =N0U2 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Carlos E. R. wrote:
So now I have to use "make install" directly on my systems without creating the rpm. :-(
Then install in /usr/local and use stow for easy de-install... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2017-03-09 17:03, Peter Suetterlin wrote:
Carlos E. R. wrote:
So now I have to use "make install" directly on my systems without creating the rpm. :-(
Then install in /usr/local and use stow for easy de-install...
I just installed it to have a look at the man page. stow - software package installation manager I can't try it now, headache. - -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAljCxeoACgkQja8UbcUWM1yAcwD/a7bK8WJasghJrHqdNEioGx/b HX4yabKy8nDpEOtKIzQA/jRe8Md/X/sfBVRVXpPXHEL3AesddfwrXaQ9uViza+tS =l04h -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (14)
-
Carlos E. R. -
Chan Ju Ping -
Freek de Kruijf -
Greg Freemyer -
Jan Engelhardt -
Knurpht - Gertjan Lettink -
Ludwig Nussel -
Luiz Fernando Ranghetti -
Malcolm -
Mark Goldstein -
Martin Pluskal -
Michal Kubecek -
Peter Suetterlin -
Stefan Seyfried