From: David E. W. <da...@ju...> - 2014-01-28 22:19:21
|
Hi Mason, On Jan 28, 2014, at 1:28 PM, Mason Sharp <ms...@tr...> wrote: > Let me know what you have in mind. Are you interested in maintaining the XC RPMs? I’m interested in helping to make XC RPMs available in exactly the same way as PostgreSQL RPMs are provided by yum.postgresql.org, which would also allow RPMs to be created for extensions built against XC. I don't want to do all the maintenance myself, but would be happy to work with you and the PGRPMs guys going forward. The main question would be how to name things. PGRPMs attaches the major version number to all RPMs built against it. So you have postgresql93, of course, but then also postgis93, pgtap93, etc. This is so that they can have multiple versions at the same time, without conflict. So there is also postgressql92 with postgis92 and pgtap92 built against it. I don't think it would make sense to have postgresxc11 and then postgis11 and pgtap11, because what if there was eventually an XC 9.3? What would the postgis and pgtap extensions built against it be called? I do think it makes sense to append “xc11” instead of “11”, so we’d have postgresxc11, postgisxc11, and pgtapxc11. Thoughts? > Also, are you using XC in production? Dev/test? I built these RPMs (not knowing you had already done it) in order to simplify things for a four-server test configuration I’m building. But also because I expect the test to go well, in which case we will be looking at building reporting and/or analytics clusters on XC in the next six months. I expect to ask many ignorant questions in the next few weeks. :-) Best, David |