Re: SuSE RPMs available for PostgreSQL 7.4
От | Peter Eisentraut |
---|---|
Тема | Re: SuSE RPMs available for PostgreSQL 7.4 |
Дата | |
Msg-id | Pine.LNX.4.44.0311191837170.21224-100000@peter.localdomain обсуждение исходный текст |
Ответ на | Re: SuSE RPMs available for PostgreSQL 7.4 (Lamar Owen <lowen@pari.edu>) |
Ответы |
Re: SuSE RPMs available for PostgreSQL 7.4
|
Список | pgsql-general |
Lamar Owen writes: > The place they were put. The 'customary place' has been > v{version}/RPMS/{distribution} so that they would be in > pub/binary/v7.4/RPMS/suse-{version}. Their source RPM would go there too. My reverse engineering attempt at the existing custom went as follows: I saw SRPMS containing a source RPM distrib-1 above source RPM built for that distribution distrib-2 above source RPM built for that distribution So since this RPM set uses a different source RPM, one solution would have been SRPMS containing more than one source RPM distrib-1 one of the above source RPMs built for that distribution distrib-2 one of the above source RPMs built for that distribution But that seems unnecessarily confusing. You seem to propose this solution: SRPMS containing a source RPM distrib-1 above source RPM built for that distribution distrib-2 above source RPM built for that distribution other-distrib containing different source RPM and binary RPM But that is assymetric. So the solution was to put each RPM set, consisting of a source RPM and binaries built from it, in its own subdirectory. That solution also has the advantage that if someone wanted to post other binaries, say for Debian or Solaris, they could become a peer directory of "suse". That way, someone looking for binaries could follow the name of the operating system and would not have to know details about which packaging system is used. -- Peter Eisentraut peter_e@gmx.net
В списке pgsql-general по дате отправления: