Question about BuildArch and rpmrc on 64-bit

[Archie]

Thanks, travisn000. Yeap, I can download. Will test it out and report.

[travisN000]

Thanks..

Also,  if any one has issues installing the new RPM's by using an old pkgutils context menu shortcut, try installing it from console by hand (..for some reason mkrepo when installed via right click option has issues connecting to the X session for zenity prompts...  it will work fine if you open a console manually though)


And here is a brief changelog (I forgot to update it in the spec  ):

Code: [Select]

%changelog
* Tue Nov 15 2011 travisn000 <forumUserName at gmail dot com> 0.1.6-1
- spec set as noarch
- updated mkrepo script:
+ ..will configure for either 32 or 64 bit build automatically
- added additional context menu items (and scripts) to -kde package
+ ...feature parity with thunar version
+ ..'install rpm/srpm' options now support URLs.. right click to install from net in konqueror!
+ ..build, build/log, compress to xz/tar, and recompress_to_tarxz all support batch operations in KDE4
 


[Archie]

Removed previous pkgutils and installed 0.1.6 without problems both on VirtualBox Minime 32 and a 64-bit install on a machine.

Build All is OK.

Install Dependencies I think is still broken because it did not install needed packages
List Check was giving out File not found errors on package that already built.

Will test more.

[Neal ManBear]

Another method of installation is to install Leiche's RPM Installer package.     

[Archie]

Another method of installation is to install Leiche's RPM Installer package.     

Hmmm, that package wasn't installed. Doing it now. Thanks, Neal.

[travisN000]

Install Dependencies I think is still broken because it did not install needed packages
List Check was giving out File not found errors on package that already built.

I will look into this one...

Also, I just uploaded slightly updated packages (same link)..  just a small change to the " re-compress as xz" script so that it better handles large source.tar's and handles source.tar's that don't have a primary directory matching the name of the tar.

[travisN000]

Install Dependencies I think is still broken because it did not install needed packages

The above is fixed.. download link is the same.

List Check was giving out File not found errors on package that already built.

I believe this is normal behavior... the should be the same if you ran "rpmbuild -bl <specfile>" in console for the same spec.  If you use the "prep, compile, and Install" option first you wont get this...
 

[travisN000]

One last update... Tex dug up a more recent SRPM than the one I started with;  they are now merged:

...download link is the same, if no other problems are found I will send this one to Tex as final.

[Archie]

Heya Travis,

Apart from the update which I now have installed and still have to be tested, I just like to point out a few things that might help improve the package.

On the update side, wouldn't it be better for pkgutils to check if there is already an exisiting .rpmmacros and .rpmrc, and have the option to review the changes if any? The same thing with mkrepo.

I do not know about the other packagers but I have an unconventional setup and do not have my /src folder right directly under my /home/archie. It is on a subfolder, which is the way I prefer.

It's not a big deal really but the updates prompt me to double check my setup and make sure that my configuration are still in place because I do not want my RPMS saved on other locations. I also noticed that mkrepo added the /home/archie/src URI and I already have one that I use and what was needed to be added was the i586, athlon and noarch section along with the x86_64.

I understand that it would take a lot of time to modify the script and I am not asking you nor anyone to change it. I am aware of it and I can make the appropriate adjustments on my end. I also understand that standardizing the build environment would have its advantages, especially to users starting to learn to package.

I am just pointing it out so maybe someday someone (hopefully Martin) would be able to further improve this already excellent tool.

Regards.

[travisN000]

This should be pretty easy to add...  I considered changing the directory name to something more descriptive like rpmbuild, but didn't want it to mess with others that are standardized on src..
 

[Archie]

This should be pretty easy to add...  I considered changing the directory name to something more descriptive like rpmbuild, but didn't want it to mess with others that are standardized on src..
 

Understood.

Overall, on the few checks I have done, it looks good and no anomalies to report.

List Check was giving out File not found errors on package that already built.

I believe this is normal behavior... the should be the same if you ran "rpmbuild -bl <specfile>" in console for the same spec.  If you use the "prep, compile, and Install" option first you wont get this...
 

Checked and got a list of dependencies. 

Another method of installation is to install Leiche's RPM Installer package.     

Hmmm, that package wasn't installed. Doing it now. Thanks, Neal.

This additional package provided an extra item on my KDE menu. Software Center > RPM-show info ... and it's surely a MUST for anyone packaging IMO.

Thank you, travisn000 for getting this done. I'm sure others like myself owe you a pint of lager for your efforts.

[Neal ManBear]

This additional package provided an extra item on my KDE menu. Software Center > RPM-show info ... and it's surely a MUST for anyone packaging IMO.

     
Yes. I agree with that.     
RPM Installer is one of the first packages I install, when I set up a build/packaging environment. There is an excellent right click > install menu that comes with pkgutils, but I like the 'extras' that come with RPM Installer.      

[travisN000]

This additional package provided an extra item on my KDE menu. Software Center > RPM-show info ... and it's surely a MUST for anyone packaging IMO.

     
Yes. I agree with that.     
RPM Installer is one of the first packages I install, when I set up a build/packaging environment. There is an excellent right click > install menu that comes with pkgutils, but I like the 'extras' that come with RPM Installer.      

..should I add it to the dependency list?  That would ensure it gets installed by those like me that didn't know of it...

[Archie]

Yes. I agree with that.     
RPM Installer is one of the first packages I install, when I set up a build/packaging environment. There is an excellent right click > install menu that comes with pkgutils, but I like the 'extras' that come with RPM Installer.      

..should I add it to the dependency list?  That would ensure it gets installed by those like me that didn't know of it...

I would vote yes on that.

[Neal ManBear]

Yes. I agree with that.     
RPM Installer is one of the first packages I install, when I set up a build/packaging environment. There is an excellent right click > install menu that comes with pkgutils, but I like the 'extras' that come with RPM Installer.      

..should I add it to the dependency list?  That would ensure it gets installed by those like me that didn't know of it...

I would vote yes on that.

     
My vote:     
+1!