| 1 |
On 2018-02-27 12:45, Rich Freeman wrote: |
| 2 |
|
| 3 |
> I use --with-bdeps=n because I really don't care that much about |
| 4 |
> build-time deps, other than stuff that is going to get updated anyway |
| 5 |
> like gcc. These packages don't even need to be installed for software |
| 6 |
> to work correctly, and if a dev does miss an RDEPEND there is a decent |
| 7 |
> chance they'll miss it in DEPEND also. |
| 8 |
|
| 9 |
Ok, so this looks like the relevant one in the current mess, at least. |
| 10 |
But: if you omit --with-bdeps, what happens in the (relatively frequent) |
| 11 |
situation when an already installed package is being updated and |
| 12 |
acquired a new build dependency, which is not yet installed? |
| 13 |
|
| 14 |
-- |
| 15 |
Please don't Cc: me privately on mailing lists and Usenet, |
| 16 |
if you also post the followup to the list or newsgroup. |
| 17 |
To reply privately _only_ on Usenet and on broken lists |
| 18 |
which rewrite From, fetch the TXT record for no-use.mooo.com. |
Archives