Welcome to Our New Packagers

[mmesantos1]

Hi Neal,
Yes I have read this, I am aware of removing the branding which is why I need to build the certain packages from source to add my own branding. I do not plan on selling my OS but wanted the whole OS to be consistently branded and when packages are updated did not want the branding to revert back to PCLinuxOS. I want to stay within the guidelines Texstar has given. 

I just wanted to be sure you had the info. IMO, I would be remiss, if I held back important info like that.

Thank you Neal for the information. I appreciate your intent in giving the information. 

[MBantz]

Ok so I want to say hello to all. Also I am very green when it comes to this stuff so if my questions do not make sense I will say I am sorry right now.

So lets get to it, I am learning this packaging thing so I can build my own versions of certain packages to brand them for the OS I am making. I am using the PCLinuxOS KDE Minime as the base for my OS so the package building should work for me.
I had a question on the need to add testing to the end of the repo on my build OS I have installed. Was wondering why I need the testing repo VS. the stable one, as I am only building the package to re-brand it will this still be necessary. If why, I did not see a why when reading the how to wiki guide I got from this thread. Just want to know why I am doing this. I want to say thank you in advance for your help with my question.  

Marc

I can not recommend to use testing when building, then testing packages is mixed and all sorts of issues can arise from this. Where does it say this in the wiki?
Of course, it can happen that a needed library is in testing, then it's ok to pull this one library - and perhaps wait to send the package to the repo until the library is actually out of testing,

cheers,
MBantz

Hi MBantz,
The guide I am refering to is from this link: http://www.montanalinux.org/files/RPM_Build_Manual_Rev2.pdf

From the 2nd post in this thread. From reading it it sounds like this is a needed step. I would quote the steps from the guide but I am at work and unable to open the PDF from my workstation now. But towards the beginning of the guide when you are preparing the build environment it makes mention of adding Testing to your repo selected in the sources list. I was confused why they gave this as a required step but they did not state why. This is why I posted my original question. Did not intend on breaking forum rules.

Ok, the setup part of the guide should not be followed, it's error prone to follow - and I also can't understand the recommendation on using the testing repo.

Everything is setup properly when installing the pkgutils package,

cheers,
MBantz

[Neal ManBear]

It is recommended that you not use testing, unless you can repair your system, if something breaks. Testing is not stable; it is called testing for the reason that the apps need to be tested for bugs, etc and to find out how/when they can be moved to stable.

Passing on apps in testing to regular users is a bad idea. If you do that, and something breaks, who do you think will be blamed?

[mmesantos1]

Thank you MBantz and Neal, I thought that sounded strange when I read it but wanted to make sure. You may want to edit or remove this guide from this thread then as someone may not ask after reading and use the steps. Just a thought. 

Marc

[Joble]

Testing is where the packaging file used to be kept.  They are in the main repository now and the entire process for setting up the environment is automagic.  Also with the new apt and rpm pretty much everything will change.  Yeah, prolly best to remove the guide as it is too antiquated to be of much real use any more.

[mmesantos1]

Testing is where the packaging file used to be kept.  They are in the main repository now and the entire process for setting up the environment is automagic.  Also with the new apt and rpm pretty much everything will change.  Yeah, prolly best to remove the guide as it is too antiquated to be of much real use any more.

Thank you Joble, will there be an updated guide put out for this process?

[timeth]

Hi packagers,

Just trying to set up the build environment on my new LXDE install. When I mark pkgutils for installation in synaptic, I get this error >

Code: [Select]

pkgutils:
 Depends: rpm-build
 Depends: rpm-pclinuxos-setup-build
Then when I try to install pkgutils-thunar, I get this >

Code: [Select]

pkgutils-thunar:
 Depends: pkgutils
And when I try to install pkgutils-kde4, I get this >

Code: [Select]

pkgutils-kde4:
 Depends: pkgutils
So then I tried to install rpm-build and I get this >

Code: [Select]

rpm-build:
 Depends: rpm (= 4.4.6-18pclos2007)
 Depends: rpm-mandriva-setup-build

A can't seem to install anything that will set up the build environment.  
Does anyone have some ideas about this?

[djohnston]

I think I saw an earlier post from gseaman that he's working on the pkgutils right now. Hopefully, he or someone else will chime in.

[gseaman]

I usually stick to applications and not system utilities and libraries. For pkgutils and the other pkg apps, I think the issue is that some of the dependencies have been moved to the unstable section. I'm suspect that Tex will move everything once all of the yum, yumex, etc. packages are ready. If I tried to make pkgutils work in this temporary state, it would be likely broken shortly after I finished.

Galen

[timeth]

Thanks djohnston and Galen,

Understood. I'll hang out for a bit until they're ready to go.

[muungwana]

any updated on this "pkgutils" package?

I tried to install it and i am also getting complains on missing dependencies.

[Neal ManBear]

any updated on this "pkgutils" package?

I tried to install it and i am also getting complains on missing dependencies.

You have to enable 'unstable' to install pkgutils.     

[glamdring]

any updated on this "pkgutils" package?

I tried to install it and i am also getting complains on missing dependencies.

You have to enable 'unstable' to install pkgutils.     

How can I enable 'unstable' packages?

[Neal ManBear]

Synaptic > Settings > Repositories >>> Sections: --- add unstable at the end of the line >> Reload. When finished, remove unstable and again reload.     

Note: Do not update from unstable. Notice the name.     

[Yankee]

Be sure to bookmark the RPM How-To. Even if you have learned it all very well, you'll want to use it as a reference.

Hi,

Searched for RPM How-To and it keeps referring back to this message.
Want to be sure I have the most current place.   Do you have a current
link to bookmark ?   Are docs with the pkgutil package ?    Haven't
installed anything yet.

THX.