Re: debian/upstream and the PTS.
Hi Charles,
On Sat, 27 Apr 2013, Charles Plessy wrote:
> - We use it in Debian Med, and there is currently no replacement availalbe.
>
> - If a superior solution emerges, I am happy to use it, and I am sure
> that it will be the case of the other Debian Med members.
Thanks for confirming this. I know that you already have it working and I
respect the do-ocracy, that's why I didn't try to stop anyone from getting
this implemented. But I truly believe that we need a better interface
to collect and export such metadatas.
> - Monitoring the package's VCS is a key feature: it gives ACLs for free, and
> removes the need for uploading source packages. For Debian Med, all Debian
> developers have write access to our VCS. I would be happy to extend this to
> all Alioth users, but it has been discouraged in the past.
I know the benefits of using the VCS, but it's still a poor choice because
I trust almost everybody to edit upstream metadata but I wouldn't trust
everybody with commit rights to my package.
Also, inspecting VCS is more heavy than say querying the PTS with a REST
interface.
> - The DEP is a draft, about fixing the syntax of debian/upstream. It is not a
> proposition about an implementation, because it is already implemented. How
> the data is further propagated is also out of the scope of this DEP. (Which
> does not mean that it is not important or that it should not be discussed,
> of course).
The fact that you need a syntax is a consequence of the choice you made to
store it in a file in a VCS. Thus the DEP is a bit flawed from the start
IMO.
> debian/upstream concept, but in the meantime, let's avoid "chilling effects" of
> better solutions awaiting for an implementation.
Certainly!
Cheers,
--
Raphaël Hertzog ◈ Debian Developer
Get the Debian Administrator's Handbook:
→ http://debian-handbook.info/get/
Reply to: