Jonathan Hall <j...@nmgi.com> writes:
> Frans Pop wrote:
>> Note also that the "local" component is already being handled
>> separately.
>>
> That brings up another question... should I simply add a
> CUSTOM_COMPONENTS feature, or should I merge the exiting
> LOCAL/LOCALDEBS features into the new CUSTOM_COMPONENTS option, thus
> simplifying configuration, while possibly breaking backward
> compatibility of configuration files (Is that a concern with a project
> like this anyway)?
If it is mergeable, it is better to merge it.
backward compatibility is always good. I think it's going to be easy
to provide it in this case. Maybe would be nice to warn during the
build about the new configuration to allow the dropping of it in
future.
--
O T A V I O S A L V A D O R
---------------------------------------------
E-mail: ota...@debian.org UIN: 5906116
GNU/Linux User: 239058 GPG ID: 49A5F855
Home Page: http://otavio.ossystems.com.br
---------------------------------------------
"Microsoft sells you Windows ... Linux gives
you the whole house."
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
