| 1 |
On 2016-06-02(04:37:00+0000), James wrote: |
| 2 |
> ng0 <ng0 <at> n0.is> writes: |
| 3 |
> |
| 4 |
> > > Is there a consistent semantic to at least list all of the portage tree |
| 5 |
> > > packages there are listed on as maintainer? |
| 6 |
> > > Is there a universal, slick way to list the overlay packages they are |
| 7 |
> > > working on (github)? |
| 8 |
> |
| 9 |
> > What about checking out the portage repo and doing the native git search |
| 10 |
> > in there via log? |
| 11 |
> |
| 12 |
> I was actually hoping for something much simpler and always as current as the |
| 13 |
> last sync of protage and the corresponding overlays (layman syntax). Perhaps |
| 14 |
> an option I missed in the 'q' applets (portage-utils) or gentoolkit ? |
| 15 |
> |
| 16 |
> |
| 17 |
> If nothing exist, I'd consider writing some C (q applets) or python |
| 18 |
> (gentoolkit) code to perform this searching task. It wont be comprehensive, |
| 19 |
> but it should work on both the protage tree and the official overlays. |
| 20 |
> |
| 21 |
> |
| 22 |
> Thoughts and ideas are welcome. |
| 23 |
> |
| 24 |
> |
| 25 |
> James |
| 26 |
|
| 27 |
I'm not sure if it works like this. |
| 28 |
You have the metadata.xml files and Changelog files, as far as I know those |
| 29 |
are the only name -> package relations you can get when not using git. |
| 30 |
|
| 31 |
I might be wrong, so a tool like this could be useful if one needs it. |
| 32 |
|
| 33 |
-- |
| 34 |
♥Ⓐ ng0 |
| 35 |
4096R/13212A27975AF07677A29F7002A296150C201823 |
Archives