I seem completely lost

[Neal ManBear]

If anyone, whoever it might be, chooses to write a how to/manual for building RPMs, before it is published, you will need to have it reviewed and edit it. You will need to upload it somewhere - your dropbox folder is good - and post a link in a new topic here. In this way, it can be reviewed and replies with corrections/suggestions for rewording can be made.     

Please do not publish a how to/manual for building RPMs to pclinuxoshelp (our knowledgebase/wiki) without first having it reviewed and edited here. If you do, I will request that it be removed. Remember, this is about PCLinuxOS, building rpms to PCLinuxOS standards and sharing with the community.     

[Archie]

Here's an idea, Neal ...

Since I've always put a stress on collaboration, we can all chip in at what the howto/documentation needs to make it as comprehensive as possible. In ways, it is the collective knowledge that would make it complete and acceptable.

One member will miss out on one or few things but when we all chip in, we can be assured that all your bases are belong to us.

[Neal ManBear]

Here's an idea, Neal ...

Since I've always put a stress on collaboration, we can all chip in at what the howto/documentation needs to make it as comprehensive as possible. In ways, it is the collective knowledge that would make it complete and acceptable.

One member will miss out on one or few things but when we all chip in, we can be assured that all your bases are belong to us.

     
  That is why I said any how to/manual for building RPMs needed to be reviewed/edited via a new thread here before being published.     

[on4aa]

I'm not sure with what you want start, i started with a own script-tool (system-info), and read this sorry found it only in german, this link will not longer work http://www.montanalinux.org/files/RPM_Build_Manual_Rev2.pdf.

Thanks. I already had found RPM_Build_Manual_Rev2.pdf. It is well written, but appears not to be completely up to date.
If I am not mistaken, there is no mention about pkgutils etc. The German wiki/HTML version is a bit better but still not up to date.
I have also found some information on the Dutch PCLinuxOS forum. I will try to assimilate this information in the coming days.

[Neal ManBear]

on4aa,     
We know the manual was written before pkgutils was available; i.e. we know it is out of date. That is why we have been discussing a rewrite.     

[on4aa]

Since I've always put a stress on collaboration, we can all chip in at what the howto/documentation needs to make it as comprehensive as possible. In ways, it is the collective knowledge that would make it complete and acceptable.

One member will miss out on one or few things but when we all chip in, we can be assured that all your bases are belong to us.

Forgive me for having stirred up things here as a newcomer... and for giving Archie some work to do
Perhaps you guys should have a look at http://techmonks.net/working-together-on-text-and-source-code-with-gobby-and-infinoted/ and
https://secure.wikimedia.org/wikipedia/en/wiki/Gobby

Gobby (the client) and infinoted (the server deamon) allow team members to edit text or source code simultaneously and chat over IRC whilst working at it. It might be a great tool for the task at hand.

(BEWARE this is a package request in disguise  )

[Neal ManBear]

on4aa,   
  We're already working our collective butts off. Package Suggest is closed!      

We already have a collaborative method. If you reread what Archie and I wrote, you will see what it is. We will do this rewrite here, in the community, not in some other place.     

PCLinuxOS has methods and standards. Special access is not needed for this section of the forum. It is open to the community.     

[Archie]

on4aa,   
  We're already working our collective butts off. Package Suggest is closed!      

We already have a collaborative method. If you reread what Archie and I wrote, you will see what it is. We will do this rewrite here, in the community, not in some other place.     

PCLinuxOS has methods and standards. Special access is not needed for this section of the forum. It is open to the community.     

Just the way I like it ... transparent. Everyone can read, everyone can try.

@on4aa, check this section for the recent changes in packaging. Read the Mighty Texstar's posts and announcements. Setting up a build environment is not as manually confusing as it was on Rev2. Stuff and commands gets automated and find themselves in service menus.

That's all for now.

Peace and much respect,
Archie