On Sun, Jul 03, 2022 at 09:03:04PM -0700, Georgy Yakovlev wrote:
> I've been rather busy lately and can't keep up with all of my packages.
> There are pending bumps, some bugs, but nothing too crazy or hard.
> So I'm looking for someone to co-maintain (or even take over if you
> insist) the follow
On Sun, Jul 03, 2022 at 09:03:04PM -0700, Georgy Yakovlev wrote:
> I've been rather busy lately and can't keep up with all of my packages.
> There are pending bumps, some bugs, but nothing too crazy or hard.
> So I'm looking for someone to co-maintain (or even take over if you
> insist) the follow
On Tue, Jul 5, 2022 at 3:02 PM Georgy Yakovlev wrote:
>
> ...snip
> >
> > > In that case, I think the only viable way to make this work is to
> > > disable automatic stripping and handle stripping via custom code in
> > > the ebuild/eclass.
> > >
> > might work indeed if we do something like (pseu
On 22/07/05 12:02PM, Georgy Yakovlev wrote:
> started playing with my old code and got blocked right away:
>
> looks like dostrip just creates a list of files/directories to strip
> and processed at the very end of install phase.
>
> so skipping strip and doing manual one might be problematic.
>
...snip
>
> > In that case, I think the only viable way to make this work is to
> > disable automatic stripping and handle stripping via custom code in
> > the ebuild/eclass.
> >
> might work indeed if we do something like (pseudo-bash)
>
> if [[ module_sign == yes ]]; then
> dostrip -x /lib
