Hi all.
I'd like to put together a small repo for Centos packages that I build on my machine, and make them available for other Centos users.
Are there any guidlines for creating an officially endorsed Centos 3rd party repo please?
Kind Regards,
Keith Roberts
----------------------------------------------------------------- Websites: http://www.karsites.net http://www.php-debuggers.net http://www.raised-from-the-dead.org.uk
All email addresses are challenge-response protected with TMDA [http://tmda.net] -----------------------------------------------------------------
Keith Roberts wrote:
Hi all.
I'd like to put together a small repo for Centos packages that I build on my machine, and make them available for other Centos users.
Are there any guidlines for creating an officially endorsed Centos 3rd party repo please?
Kind Regards,
Keith Roberts
Officially endorsed is the problem part. I do not think you will receive that.
You could be added to http://wiki.centos.org/AdditionalResources/Repositories list, but even my repo and few others is not up there.
Important part is to sign each packages so people truest it more. I never had time for that, but it is highly advisable if you want to be trusted.
Ljubomir
On 20/05/11 13:31, Keith Roberts wrote:
Hi all.
I'd like to put together a small repo for Centos packages that I build on my machine, and make them available for other Centos users.
Are there any guidlines for creating an officially endorsed Centos 3rd party repo please?
Kind Regards,
Keith Roberts
No, because CentOS will not officially endorse anything that it does not build (and sign) itself.
You are talking about a community 3rd party repo. Rather than reinvent the wheel, why don't you just contribute (and maintain) your packages in an existing repository. RPMforge would be a good choice and I'm sure would welcome your contribution.
What packages did you have in mind? Are you sure they don't exist somewhere already?
On Fri, 20 May 2011, Ned Slider wrote:
To: CentOS mailing list centos@centos.org From: Ned Slider ned@unixmail.co.uk Subject: Re: [CentOS] Creating a Centos endorsed 3rd part repo
On 20/05/11 13:31, Keith Roberts wrote:
Hi all.
I'd like to put together a small repo for Centos packages that I build on my machine, and make them available for other Centos users.
Are there any guidlines for creating an officially endorsed Centos 3rd party repo please?
Kind Regards,
Keith Roberts
No, because CentOS will not officially endorse anything that it does not build (and sign) itself.
OK - I can understand the reasons for that :)
You are talking about a community 3rd party repo. Rather than reinvent the wheel, why don't you just contribute (and maintain) your packages in an existing repository. RPMforge would be a good choice and I'm sure would welcome your contribution.
I'm sure they would Ned. But I want to learn how to do the whole repository thing myself - not just build packages for another very good 3rd party repo.
What packages did you have in mind? Are you sure they don't exist somewhere already?
Things like qps and the latest version of Kompozer.
So are there any guidlines on creating a community 3rd party repo that would make it into the Centos Wiki pages please?
Kind Regards,
Keith
----------------------------------------------------------------- Websites: http://www.karsites.net http://www.php-debuggers.net http://www.raised-from-the-dead.org.uk
All email addresses are challenge-response protected with TMDA [http://tmda.net] -----------------------------------------------------------------
So are there any guidlines on creating a community 3rd party repo that would make it into the Centos Wiki pages please?
Not for getting you on that list, but...
If you plan on being the only one releasing, then just use mrepo and set it to output to directory where your domain will reside. Symlinks are OK too.
But most of all learn how to sign your packages. Without that you will get no where near that list.
Ljubomir
On Fri, 20 May 2011, Keith Roberts wrote:
I'm sure they would Ned. But I want to learn how to do the whole repository thing myself - not just build packages for another very good 3rd party repo.
There really is nothing to creating a repo that's hard in itself. createrepo/mrepo an rpmsign and you're done.
By all means do that for internal use, but I'd second the suggestion that you find a way of contributing your packages to an existing repo rather than start your own.
jh
On 5/20/2011 10:15 AM, John Hodrien wrote:
On Fri, 20 May 2011, Keith Roberts wrote:
I'm sure they would Ned. But I want to learn how to do the whole repository thing myself - not just build packages for another very good 3rd party repo.
There really is nothing to creating a repo that's hard in itself. createrepo/mrepo an rpmsign and you're done.
By all means do that for internal use, but I'd second the suggestion that you find a way of contributing your packages to an existing repo rather than start your own.
I'll second that suggestion. The more 3rd party repos that you add to the yum config, the more possible conflicts you open yourself up to. Besides, it's easier to find packages if they are all in one or two places rather than spread out across several small repos.
On Fri, 20 May 2011, Bowie Bailey wrote:
To: centos@centos.org From: Bowie Bailey Bowie_Bailey@BUC.com Subject: Re: [CentOS] Creating a Centos endorsed 3rd part repo
On 5/20/2011 10:15 AM, John Hodrien wrote:
On Fri, 20 May 2011, Keith Roberts wrote:
I'm sure they would Ned. But I want to learn how to do the whole repository thing myself - not just build packages for another very good 3rd party repo.
There really is nothing to creating a repo that's hard in itself. createrepo/mrepo an rpmsign and you're done.
By all means do that for internal use, but I'd second the suggestion that you find a way of contributing your packages to an existing repo rather than start your own.
I'll second that suggestion. The more 3rd party repos that you add to the yum config, the more possible conflicts you open yourself up to. Besides, it's easier to find packages if they are all in one or two places rather than spread out across several small repos.
OK. I am listening to all your comments. My repo would be using dependencies probably from the other centos repos, like ATrpms, remi, EPEL, et al. If they needed any that is.
Kind Regards,
Keith Roberts
----------------------------------------------------------------- Websites: http://www.karsites.net http://www.php-debuggers.net http://www.raised-from-the-dead.org.uk
All email addresses are challenge-response protected with TMDA [http://tmda.net] -----------------------------------------------------------------
Keith Roberts wrote:
On Fri, 20 May 2011, Bowie Bailey wrote:
To: centos@centos.org From: Bowie Bailey Bowie_Bailey@BUC.com Subject: Re: [CentOS] Creating a Centos endorsed 3rd part repo
On 5/20/2011 10:15 AM, John Hodrien wrote:
On Fri, 20 May 2011, Keith Roberts wrote:
I'm sure they would Ned. But I want to learn how to do the whole repository thing myself - not just build packages for another very good 3rd party repo.
There really is nothing to creating a repo that's hard in itself. createrepo/mrepo an rpmsign and you're done.
By all means do that for internal use, but I'd second the suggestion that you find a way of contributing your packages to an existing repo rather than start your own.
I'll second that suggestion. The more 3rd party repos that you add to the yum config, the more possible conflicts you open yourself up to. Besides, it's easier to find packages if they are all in one or two places rather than spread out across several small repos.
OK. I am listening to all your comments. My repo would be using dependencies probably from the other centos repos, like ATrpms, remi, EPEL, et al. If they needed any that is.
Why not work with Dag?
mark
Keith Roberts wrote on 05/20/2011 10:57 AM:
OK. I am listening to all your comments. My repo would be using dependencies probably from the other centos repos, like ATrpms, remi, EPEL, et al. If they needed any that is.
In my experience packages that need dependencies from more than one 3rd party repo tend to be problematic. The more different repos required the more problems with conflicts between repos and different packaging philosophies.
If you can confine your dependencies to at most one or two repos, then life will be easier for both you and any potential users of the packages. Again, once you have working packages, then offering to contribute and maintain them at the repo[s] on which they depend would be a good idea.
Phil
On 20/05/11 15:57, Keith Roberts wrote:
On Fri, 20 May 2011, Bowie Bailey wrote:
To: centos@centos.org From: Bowie BaileyBowie_Bailey@BUC.com Subject: Re: [CentOS] Creating a Centos endorsed 3rd part repo
On 5/20/2011 10:15 AM, John Hodrien wrote:
On Fri, 20 May 2011, Keith Roberts wrote:
I'm sure they would Ned. But I want to learn how to do the whole repository thing myself - not just build packages for another very good 3rd party repo.
There really is nothing to creating a repo that's hard in itself. createrepo/mrepo an rpmsign and you're done.
By all means do that for internal use, but I'd second the suggestion that you find a way of contributing your packages to an existing repo rather than start your own.
I'll second that suggestion. The more 3rd party repos that you add to the yum config, the more possible conflicts you open yourself up to. Besides, it's easier to find packages if they are all in one or two places rather than spread out across several small repos.
OK. I am listening to all your comments. My repo would be using dependencies probably from the other centos repos, like ATrpms, remi, EPEL, et al. If they needed any that is.
Which is an excellent reason for having your package(s) in one of those repos so they are built against the necessary dependencies if they are not already a part of CentOS.
Otherwise you will simply be yet another example of why mixing different 3rd party repos (generally) doesn't work.
Keith Roberts wrote:
OK. I am listening to all your comments. My repo would be using dependencies probably from the other centos repos, like ATrpms, remi, EPEL, et al. If they needed any that is.
If you need to rely on other third party repos, and you are set on intent to have your own repo, then you will need your own release package and you might find necessity to distribute yum configuration files for other repositories with priority plugin enabled (like I did for my repo) and create security nightmare and distrust of general public, or to create installation script like virtualmin/webmin does.
I created the set of release packages and a script that backups current set of yum config files and replaces them with config files created for particular use.
For example, for use on servers I compiled main centOS repositories including CentOS Plus, EPEL, and several of my own repositories. For desktop users I added ATrpms, RPMForge and few others like adobe and pidgin repositories. But all of those yum config files are created by me, not by the repo owners and I have excluded all of the their release files including CentOS release files.
I had to create text database file from witch I pull data and create sets of yum config files with inserted exclude and priority lines. Other option was to change yum config files for those repos by I decided this is easiest and safe for the user, but he has to trust that I will not redirect him to unsafe site with fake repository. That is why I haven't bothered with signing and was satisfied to use my repositories on system I maintain.
Ljubomir
Thanks for all the replies to my initial questions on this. It certainly has given me some food for thought.
KISS seems to be the order of the day with repos?
Regards,
Keith
----------------------------------------------------------------- Websites: http://www.karsites.net http://www.php-debuggers.net http://www.raised-from-the-dead.org.uk
All email addresses are challenge-response protected with TMDA [http://tmda.net] -----------------------------------------------------------------
-
Bowie Bailey -
John Hodrien -
Keith Roberts -
Ljubomir Ljubojevic -
m.roth＠5-cent.us -
Ned Slider -
Phil Schaffner