Hi Konrad,

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

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.

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.

Tully

On Mon, Nov 1, 2010 at 2:11 AM, Konrad Banachowicz <konradb3@gmail.com> wrote:
That sounds good.
I think that kind of packaging should be used for next release.
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".

Pozdrawiam
Konrad Banachowicz


2010/11/1 Jeremy Leibs <leibs@willowgarage.com>

On Sun, Oct 31, 2010 at 4:37 PM, Adam Leeper <aleeper@stanford.edu> wrote:
> I disagree on removing sources... they are useful for reference (if you
> can't get online) even if you aren't doing development on a package.

Once we have a valid concept of an install target within the ros build
system, I intend to automatically generate 3 debs per stack:
 - ros-<distroname>-<stackname>   will contain the minimal "installed"
version of the stack.  Executables, libs, and exported headers only.
 - ros-<distroname>-<stackname>-src  will additionally contain the
rest of the source code for the stack.
 - ros-<distroname>-<stackname>-tests  will contain the compiled
unit-tests for the stack.

>
>
> Adam Leeper
> Stanford University
> aleeper@stanford.edu
> 719.358.3804
>
>
> On Sun, Oct 31, 2010 at 12:03 PM, Konrad Banachowicz <konradb3@gmail.com>
> wrote:
>>
>> I would go further and say that sources should be removed from debs.
>> debs are not intended to be build by hand. If i want to do some devel on
>> package, I will checkout code form svn.
>> Pozdrawiam
>> Konrad Banachowicz
>>
>>
>> 2010/10/31 Konrad Banachowicz <konradb3@gmail.com>
>>>
>>> But depending on a file which should not exist is not a bug ?
>>> Pozdrawiam
>>> Konrad Banachowicz
>>>
>>>
>>> 2010/10/31 Jack O'Quin <jack.oquin@gmail.com>
>>>>
>>>> On Sun, Oct 31, 2010 at 1:06 PM, Konrad Banachowicz <konradb3@gmail.com>
>>>> wrote:
>>>> > From my point of view this will not introduce new bugs,but this could
>>>> > reveal
>>>> > existings ones.
>>>>
>>>> If something worked before, then starts failing because a file it
>>>> depended on was purged from the package, that seems like a "new bug"
>>>> to me.
>>>> --
>>>>  joq
>>>> _______________________________________________
>>>> ros-users mailing list
>>>> ros-users@code.ros.org
>>>> https://code.ros.org/mailman/listinfo/ros-users
>>>
>>
>>
>> _______________________________________________
>> ros-users mailing list
>> ros-users@code.ros.org
>> https://code.ros.org/mailman/listinfo/ros-users
>>
>
>
> _______________________________________________
> ros-users mailing list
> ros-users@code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users
>
>
_______________________________________________
ros-users mailing list
ros-users@code.ros.org
https://code.ros.org/mailman/listinfo/ros-users


_______________________________________________
ros-users mailing list
ros-users@code.ros.org
https://code.ros.org/mailman/listinfo/ros-users




--
Tully Foote
Systems Engineer
Willow Garage, Inc.
tfoote@willowgarage.com
(650) 475-2827