hi,
Background: the webstack on C4 is only available in the CentOSPlus repo since it overwrites packages from the base repo.
For the Webstack on C5, Johnny and I spoke about and want to propose changing that a little bit. Essentially, move the webstack to a subdirectory under the CentOSPlus repo and have metadata for Just the Webstack available as an option for people who dont want the rest of CentOSPlus.
The default action will remain the same. i.e. people who have the plus repo enabled, will see the entire published webstack in exactly the same way as they did for c4. Ofcourse the aim will be to ensure we get 100% dep closure on Base+Updates+WebStack as well as Base+Updates+Plus. Where Plus will include WebStack + other packages. We hope to address a few issues ( in order of importance ):
a) People moving from c4 will see no difference in the way things work
b) People who want just the webstack can see 'only' the webstack and not need to use includepkg / exclude's
c) the rsync targets from mirrors wont change, so people mirroring the plus repo will get the new packages, along with combined metadata.
The base packageset will get released to -qa soon, and most likely to testing in a few days time.
Comments ?
btw, one thing to note here - we dont want to make it a habit of building X number of repos. But since this is an extra 'product' ( for the lack of a better word to describe it ), we feel that this move would be justified this time.
On Sat, Apr 5, 2008 at 4:06 PM, Karanbir Singh mail-lists@karan.org wrote:
hi,
Background: the webstack on C4 is only available in the CentOSPlus repo since it overwrites packages from the base repo.
For the Webstack on C5, Johnny and I spoke about and want to propose changing that a little bit. Essentially, move the webstack to a subdirectory under the CentOSPlus repo and have metadata for Just the Webstack available as an option for people who dont want the rest of CentOSPlus.
The default action will remain the same. i.e. people who have the plus repo enabled, will see the entire published webstack in exactly the same way as they did for c4. Ofcourse the aim will be to ensure we get 100% dep closure on Base+Updates+WebStack as well as Base+Updates+Plus. Where Plus will include WebStack + other packages. We hope to address a few issues ( in order of importance ):
a) People moving from c4 will see no difference in the way things work
b) People who want just the webstack can see 'only' the webstack and not need to use includepkg / exclude's
c) the rsync targets from mirrors wont change, so people mirroring the plus repo will get the new packages, along with combined metadata.
The base packageset will get released to -qa soon, and most likely to testing in a few days time.
Comments ?
btw, one thing to note here - we dont want to make it a habit of building X number of repos. But since this is an extra 'product' ( for the lack of a better word to describe it ), we feel that this move would be justified this time.
I could see where X number of sub-repos might be useful for users.. but it is an extra pain to deal with without 'paying customers'. Having CentOS-Plus segregated lower as "Web, Kernel, EvolutionsFunToys" would allow people to choose what they wanted and what they didn't and having it higher up as "CentOS-Plus" shouldn't break existing setups.
So sleep-deprived grumpy conclusion: I like it. Can't think of problems at this time.
On Apr 5, 2008, at 3:06 PM, Karanbir Singh wrote:
hi,
Background: the webstack on C4 is only available in the CentOSPlus repo since it overwrites packages from the base repo.
For the Webstack on C5, Johnny and I spoke about and want to propose changing that a little bit. Essentially, move the webstack to a subdirectory under the CentOSPlus repo and have metadata for Just the Webstack available as an option for people who dont want the rest of CentOSPlus.
[...]
Comments ?
+1 -- I like this idea.
-Jeff
Karanbir Singh wrote:
The base packageset will get released to -qa soon, and most likely to testing in a few days time.
Just an update,
we had some networking issues with the build service yesterday and the packages did not get done in time. I will try and see if this can be pushed out in the next day or so.
On Sat, 5 Apr 2008, Karanbir Singh wrote:
hi,
Background: the webstack on C4 is only available in the CentOSPlus repo since it overwrites packages from the base repo.
For the Webstack on C5, Johnny and I spoke about and want to propose changing that a little bit. Essentially, move the webstack to a subdirectory under the CentOSPlus repo and have metadata for Just the Webstack available as an option for people who dont want the rest of CentOSPlus.
I am having difficulty seeing the benefit of having it as a subdirectory rather than as a separate repo that may contain the same packages hardlinked ??
I dont think mirrors restrict the repos that they mirror ??
I appreciate that it would need to be added to yum conf, but that would be the case anyway with a subdirectory.
As rhwas is a separate product I propose that we have a separate repo for it.
Lance
Lance Davis wrote:
On Sat, 5 Apr 2008, Karanbir Singh wrote:
hi,
Background: the webstack on C4 is only available in the CentOSPlus repo since it overwrites packages from the base repo.
For the Webstack on C5, Johnny and I spoke about and want to propose changing that a little bit. Essentially, move the webstack to a subdirectory under the CentOSPlus repo and have metadata for Just the Webstack available as an option for people who dont want the rest of CentOSPlus.
I am having difficulty seeing the benefit of having it as a subdirectory rather than as a separate repo that may contain the same packages hardlinked ??
I dont think mirrors restrict the repos that they mirror ??
I appreciate that it would need to be added to yum conf, but that would be the case anyway with a subdirectory.
As rhwas is a separate product I propose that we have a separate repo for it.
The difference is ...
You can point to RHWAS by itself (one level down) ... OR ... you can point to centosplus ... and in either case you get the RPMS included ... with no hardlinking required
Johnny Hughes wrote:
Lance Davis wrote:
On Sat, 5 Apr 2008, Karanbir Singh wrote:
hi,
Background: the webstack on C4 is only available in the CentOSPlus repo since it overwrites packages from the base repo.
For the Webstack on C5, Johnny and I spoke about and want to propose changing that a little bit. Essentially, move the webstack to a subdirectory under the CentOSPlus repo and have metadata for Just the Webstack available as an option for people who dont want the rest of CentOSPlus.
I am having difficulty seeing the benefit of having it as a subdirectory rather than as a separate repo that may contain the same packages hardlinked ??
I dont think mirrors restrict the repos that they mirror ??
I appreciate that it would need to be added to yum conf, but that would be the case anyway with a subdirectory.
As rhwas is a separate product I propose that we have a separate repo for it.
The difference is ...
You can point to RHWAS by itself (one level down) ... OR ... you can point to centosplus ... and in either case you get the RPMS included ... with no hardlinking required
This is DUE TO createrepo's automatic descending into directories BELOW the current directory to look for RPMS.
SO ... when you build yum metadata for centosplus ... it gets normal packages in i386 AND the RHWAS dir ... but when you run createrepo also in the RHWAS dir, you get ONLY the RHWAS RPMS in that one.
It just makes it easier for people to pick on or the other AND we don't have to maintain 2 separate paths OR remember to hardlink the files into the other path.
Lance Davis wrote:
Background: the webstack on C4 is only available in the CentOSPlus repo since it overwrites packages from the base repo.
I am having difficulty seeing the benefit of having it as a subdirectory rather than as a separate repo that may contain the same packages hardlinked ??
you dont need to hardlink packages, the metadata generation scripts will go into subdir's as well.
I dont think mirrors restrict the repos that they mirror ??
mirror.centos.org will carry all of the stuff, if external mirrors elect to only mirror parts of the tree's thats their issue surely.
I appreciate that it would need to be added to yum conf, but that would be the case anyway with a subdirectory.
It wont need to be added to yum configs for people who are using the stock CentOS yum configs, or for people moving from CentOS-4 or used to the way this package set was made available on CentOS-4
As rhwas is a separate product I propose that we have a separate repo for it.
We dont build the entire rhwas. However, if we now have this package set in an optional subrepo, we still retain the ability to get the whole of rhwas into a repo and have that setup / handled in whatever way we might want later.
To me, the biggest gain with a subrepo is that it does not change the behaviour of the CentOSPlus repo for users who have been using CentOS for a while, yet it retains the option for us to branch this stuff into something else later. If there is a need to.
The free wins we get here are that people who only want the php-5/mysql-5/pgsql8 etc stuff from the rhwas can elect to only have those and not need the entire centosplus repo enabled on their systems.