Hi Konrad, <br><br>We are targeting the removal of the build directories for the next release. To do this it does require vetting all packages planning to be built as debians to be checked for compliance. However there are many packages which don't even comply with stated best practices which means that <br>
<br>To implement the finer resolution which
Jeremy mentioned we're also working towards an install method which
could register what's source and what is necessary for runtime. However
with the multiple language support and possibly also resource files
needed, the distinction of source vs target is non trivial and thus we
are going to have to develop ways to express how to install packages.
We are actively investigating options for this, however as it's both a
technical challenge and an interface design challenge we are trying many
different options and will only roll out one which we have reviewed and
tested throughly. Especially since this sort of change is very hard to
rollback. <br>
<br>We have a strong commitment to maintaining stability for our
community. This stability is necessary for others to be able to build
on top of ROS. Please be patient as we follow our process and make sure
not to break existing code. If this is a blocker for you please let us
know and we can suggest workarounds for you problem in the short term.<br>
<br>Tully<br><br><div class="gmail_quote">On Mon, Nov 1, 2010 at 2:11 AM, Konrad Banachowicz <span dir="ltr"><<a href="mailto:konradb3@gmail.com" target="_blank">konradb3@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
That sounds good.<div>I think that kind of packaging should be used for next release.</div><div>Keeping the old scheme packages will make migration to new one more difficult, because potentially more and more packages can be build in bug "faulty way".</div>
<div><br></div><div><div>Pozdrawiam<br>Konrad Banachowicz<br>
<br><br><div class="gmail_quote">2010/11/1 Jeremy Leibs <span dir="ltr"><<a href="mailto:leibs@willowgarage.com" target="_blank">leibs@willowgarage.com</a>></span><div><div></div><div><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div>On Sun, Oct 31, 2010 at 4:37 PM, Adam Leeper <<a href="mailto:aleeper@stanford.edu" target="_blank">aleeper@stanford.edu</a>> wrote:<br>
> I disagree on removing sources... they are useful for reference (if you<br>
> can't get online) even if you aren't doing development on a package.<br>
<br>
</div>Once we have a valid concept of an install target within the ros build<br>
system, I intend to automatically generate 3 debs per stack:<br>
- ros-<distroname>-<stackname> will contain the minimal "installed"<br>
version of the stack. Executables, libs, and exported headers only.<br>
- ros-<distroname>-<stackname>-src will additionally contain the<br>
rest of the source code for the stack.<br>
- ros-<distroname>-<stackname>-tests will contain the compiled<br>
unit-tests for the stack.<br>
<div><div></div><div><br>
><br>
><br>
> Adam Leeper<br>
> Stanford University<br>
> <a href="mailto:aleeper@stanford.edu" target="_blank">aleeper@stanford.edu</a><br>
> 719.358.3804<br>
><br>
><br>
> On Sun, Oct 31, 2010 at 12:03 PM, Konrad Banachowicz <<a href="mailto:konradb3@gmail.com" target="_blank">konradb3@gmail.com</a>><br>
> wrote:<br>
>><br>
>> I would go further and say that sources should be removed from debs.<br>
>> debs are not intended to be build by hand. If i want to do some devel on<br>
>> package, I will checkout code form svn.<br>
>> Pozdrawiam<br>
>> Konrad Banachowicz<br>
>><br>
>><br>
>> 2010/10/31 Konrad Banachowicz <<a href="mailto:konradb3@gmail.com" target="_blank">konradb3@gmail.com</a>><br>
>>><br>
>>> But depending on a file which should not exist is not a bug ?<br>
>>> Pozdrawiam<br>
>>> Konrad Banachowicz<br>
>>><br>
>>><br>
>>> 2010/10/31 Jack O'Quin <<a href="mailto:jack.oquin@gmail.com" target="_blank">jack.oquin@gmail.com</a>><br>
>>>><br>
>>>> On Sun, Oct 31, 2010 at 1:06 PM, Konrad Banachowicz <<a href="mailto:konradb3@gmail.com" target="_blank">konradb3@gmail.com</a>><br>
>>>> wrote:<br>
>>>> > From my point of view this will not introduce new bugs,but this could<br>
>>>> > reveal<br>
>>>> > existings ones.<br>
>>>><br>
>>>> If something worked before, then starts failing because a file it<br>
>>>> depended on was purged from the package, that seems like a "new bug"<br>
>>>> to me.<br>
>>>> --<br>
>>>> joq<br>
>>>> _______________________________________________<br>
>>>> ros-users mailing list<br>
>>>> <a href="mailto:ros-users@code.ros.org" target="_blank">ros-users@code.ros.org</a><br>
>>>> <a href="https://code.ros.org/mailman/listinfo/ros-users" target="_blank">https://code.ros.org/mailman/listinfo/ros-users</a><br>
>>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> ros-users mailing list<br>
>> <a href="mailto:ros-users@code.ros.org" target="_blank">ros-users@code.ros.org</a><br>
>> <a href="https://code.ros.org/mailman/listinfo/ros-users" target="_blank">https://code.ros.org/mailman/listinfo/ros-users</a><br>
>><br>
><br>
><br>
> _______________________________________________<br>
> ros-users mailing list<br>
> <a href="mailto:ros-users@code.ros.org" target="_blank">ros-users@code.ros.org</a><br>
> <a href="https://code.ros.org/mailman/listinfo/ros-users" target="_blank">https://code.ros.org/mailman/listinfo/ros-users</a><br>
><br>
><br>
_______________________________________________<br>
ros-users mailing list<br>
<a href="mailto:ros-users@code.ros.org" target="_blank">ros-users@code.ros.org</a><br>
<a href="https://code.ros.org/mailman/listinfo/ros-users" target="_blank">https://code.ros.org/mailman/listinfo/ros-users</a><br>
</div></div></blockquote></div></div></div><br></div></div>
<br>_______________________________________________<br>
ros-users mailing list<br>
<a href="mailto:ros-users@code.ros.org" target="_blank">ros-users@code.ros.org</a><br>
<a href="https://code.ros.org/mailman/listinfo/ros-users" target="_blank">https://code.ros.org/mailman/listinfo/ros-users</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Tully Foote<br>Systems Engineer<br>Willow Garage, Inc.<br><a href="mailto:tfoote@willowgarage.com" target="_blank">tfoote@willowgarage.com</a><br>(650) 475-2827<br>