| 1 |
On Sat, Jul 8, 2017 at 6:39 PM, William L. Thomson Jr. |
| 2 |
<wlt-ml@××××××.com> wrote: |
| 3 |
> On Sat, 8 Jul 2017 18:30:10 -0700 |
| 4 |
> Zac Medico <zmedico@g.o> wrote: |
| 5 |
> |
| 6 |
>> On Sat, Jul 8, 2017 at 4:46 PM, William L. Thomson Jr. |
| 7 |
>> <wlt-ml@××××××.com> wrote: |
| 8 |
>> > On Sat, 8 Jul 2017 16:35:34 -0700 |
| 9 |
>> > Zac Medico <zmedico@g.o> wrote: |
| 10 |
>> > |
| 11 |
>> >> For live-rebuild, it would be |
| 12 |
>> >> much nicer to have a framework that automatically triggers rebuilds |
| 13 |
>> >> when upstream changes are detected, like smart-live-rebuild. |
| 14 |
>> > |
| 15 |
>> > Which would require some sort of check to upstream to detect |
| 16 |
>> > changes on some interval. |
| 17 |
>> |
| 18 |
>> What I imagine is an option like --newuse that rebuilds packages with |
| 19 |
>> upstream changes. I suppose you could also have an option to rebuild |
| 20 |
>> if some interval has expired since the last rebuild. |
| 21 |
> |
| 22 |
> That could be useful for all live packages without requiring a set. It |
| 23 |
> could also be used for packages that are part of a set. Like if you |
| 24 |
> have a set of live ebuilds, plus some others one your system |
| 25 |
> |
| 26 |
> emerge --live world |
| 27 |
> |
| 28 |
> Updates all live ebuilds, in a set or not. That would be useful. I tend |
| 29 |
> to avoid emerging live ebuilds due to having to always re-emerge them. |
| 30 |
> Sets would help there. But a emerge option would be even better!!! |
| 31 |
|
| 32 |
Yeah, but it's not going to happen without an EAPI/PMS extension. |
| 33 |
There needs to be a standard way for the package manager to check if |
| 34 |
there has been an upstream change for a given package since the last |
| 35 |
time it was rebuilt. |
| 36 |
|
| 37 |
> Could have cron run that, and then an interval in portage is not |
| 38 |
> necessary. |
| 39 |
|
| 40 |
Doing updates via cron is inappropriate for most scenarios. I was |
| 41 |
thinking that we'd have an option to rebuild if an interval has |
| 42 |
expired *and* there has been an upstream change. That way, you can |
| 43 |
limit the rate of rebuilds if upstream is changing very frequently. |
| 44 |
|
| 45 |
> I was more thinking some sort of hook to upstream to see if |
| 46 |
> there have been any commits or changes. No reason to rebuild a live |
| 47 |
> package if nothing changed :) |
| 48 |
|
| 49 |
Yeah, that's what I was thinking all along. That's why we need an |
| 50 |
EAPI/PMS extension, in order to implement behavior like |
| 51 |
smart-live-rebuild. |
| 52 |
-- |
| 53 |
Thanks, |
| 54 |
Zac |
Archives