[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#374029: Fixing inconsisten and unusefull Build-Depends/Conflicts definition

This one time, at band camp, Thomas Bushnell BSG said:
> Wouter Verhelst <wouter@debian.org> writes:
> > Sbuild explicitely, by design, only looks at build-depends. So in order
> > for build-depends to be useful at this time if you want a package to
> > build, you need to list mostly everything in build-depends right now
> > anyway.
> Isn't it sbuild's job to comply with policy, not the other way round?

Isn't it policy's job to reflect best current practice, not dictate it?

This line of argumentation gets a bit silly and circular rather quickly.
It might be more helpful to know why sbuild explicitly does it this way,
see if a change is feasible, and then work towards making it policy,
rather than using policy as a stick.
|   ,''`.                                            Stephen Gran |
|  : :' :                                        sgran@debian.org |
|  `. `'                        Debian user, admin, and developer |
|    `-                                     http://www.debian.org |

Attachment: signature.asc
Description: Digital signature

Reply to: