Proposal for "common" repository
От | Devrim Gündüz |
---|---|
Тема | Proposal for "common" repository |
Дата | |
Msg-id | a5bbd992684992125b4a71ba05d3bf2aaf4bcf66.camel@gunduz.org обсуждение исходный текст |
Ответы |
Re: Proposal for "common" repository
|
Список | pgsql-pkg-yum |
Hi, (First of all: This is not an April 1st thing) Currently we have two types of RPMs: Some of them are tied to a specific PostgreSQL version, and some of them are not (I will call them "common"). These common packages bring in two problems: * The current build infrastructure builds them again and again for all distros+testing repos. For example, Proj is built on v12, v12testing, v11, v11testing, v10, v10testing, v9.6, v9.6testing, and v9.5 repositories. (I'll probably stop 9.6 and 10 testing repos soon, but that is not the topic right now.) * 1 common package is kept in 9 different directories (see above), which consumes a lot of disk space. It generates lots of FTP and rsync traffic. So, to avoid these two issues, I'm inclined to make a few changes: Git repo: - Rename the current "common" directory (which handles Makefiles) to "global" directory (to avoid confusion) - Make sure that common and "non-common" packages are in separate directories in git, so I'll move many packages to a new subdir - Adjust makefiles in global, and invent new directories for those common RPMs (Should be easy by altering _srcrpmdir and _rpmdir variables there), and new targets for those common RPMs. Build servers: - Update build *and sync* scripts for the new layout - Update repo files for the new layout So, this will definitely break lots of things, but I feel like I have to bite this bullet anyway. Any comments, objections? Regards, -- Devrim Gündüz Open Source Solution Architect, Red Hat Certified Engineer Twitter: @DevrimGunduz , @DevrimGunduzTR
Вложения
В списке pgsql-pkg-yum по дате отправления: