| 1 |
2010/6/11 Marcus Priesch <marcus@××××××××××××.at>: |
| 2 |
> Hi sven, |
| 3 |
> |
| 4 |
> wouldnt it be enough to have the patch included in gentoo's shadow |
| 5 |
> ebuild - as i think its mainly relevant for gentoo folks - at least in |
| 6 |
> the meantime, until the patch gets accepted upstream ?! |
| 7 |
|
| 8 |
Well, talk to the Gentoo maintainer of the shadow suite. :-) IIRC, it was |
| 9 |
clearly said, that the patch has to go through mainstream, but you can |
| 10 |
try nevertheless. IMHO the patch really _should_ go upstream and be |
| 11 |
reviewed there as it might be relevant for security stuff. |
| 12 |
|
| 13 |
> as i assume this patch alone is not enough - as it needs tweaking the |
| 14 |
> eclass providing the eadduser & co functions also ... and therefore it's |
| 15 |
> hard to put in an overlay ... or ?!?! |
| 16 |
|
| 17 |
The procedure would be: |
| 18 |
1. Get the patch accepted either upstream or in the portage tree. |
| 19 |
2. Find a good check to distinguish --chroot enabled and disabled shadow |
| 20 |
3. Modify the eclass accordingly. |
| 21 |
|
| 22 |
So, start with 1. and the rest will happen automatically... ;-) |
| 23 |
|
| 24 |
Sven |
Archives