Re: RFC: Standardizing source package artifacts build paths
Sean Whitton:
> Hello,
>
> On Tue 14 Apr 2020 at 10:54AM +02, Niels Thykier wrote:
>
>> Guillem and I have debated this and come to a solution, which we believe
>> will be able to address the concerns about the path being "hidden". It
>> also enables us to simplify parts of the migration in some cases.
>
> Thank you for your continued efforts!
>
Thanks. :)
>> The short version of that solution is to enable debhelper to expose the
>> relevant directories where you want it and under debian/.build at the
>> same time (the latter being a symlink to the former)[1].
>
> Sorry, but don't you mean the former (non-dotdirs) being a symlink to
> the latter (.build)?
>
Originally, no. Though I think I will leave it unspecified while we
experiment to see if I become wiser on the topic than I am today.
My thought was this would enable debhelper to see that the directory was
exposed and look it up without additional state tracking (which would in
turn enable debhelper to ensure that we clean up properly since both
"ends" must be removed during clean).
But worst case, it will cost me a compat level to flip the order of the
two if the epiphany comes to me after initial deployment.
~Niels
Reply to: