Re: RFC: Extension Packaging & Lookup
От | David E. Wheeler |
---|---|
Тема | Re: RFC: Extension Packaging & Lookup |
Дата | |
Msg-id | CFDC94E6-2207-4B6D-8F8B-5C427C186809@justatheory.com обсуждение исходный текст |
Ответ на | Re: RFC: Extension Packaging & Lookup ("Tristan Partin" <tristan@partin.io>) |
Список | pgsql-hackers |
On Oct 29, 2024, at 13:40, Tristan Partin <tristan@partin.io> wrote: > The backend would create the packages and publish them to the various repositories. We would probably need to come up witha dependency manifest that listed both build and runtime dependencies. > > This would need some massaging, and has various caveats like require using a well-known build system like PGXS or meson.There are probably security implications that need to be worked through. The packaging team could maybe have some burdenlifted off their shoulders. > > Is that something people would be interested in? As someone who writes software, I largely find reaching the distributionchannels is always the hardest part. Yes, I’m hoping to provide the infrastructure to enable a pattern like this as part of the PGXN v2 project. Some detailsfrom the Architecture doc[1]. However, I think this is a bit off-topic for this thread, where I’d like to try to account for issues to be addressed bythe proposed extension directory structure and search path. Best, David [1]: https://wiki.postgresql.org/wiki/PGXN_v2/Architecture#Packaging
В списке pgsql-hackers по дате отправления: