Re: [gentoo-user] Strategies for testing an ebuild

[tastytea]

On 2020-10-20 11:01-0700 Anton  wrote:

> Hi there,
> 
> I am taking on maintaining a package in gentoo-sci overlay. What are 
> good ways to test that my ebuild works before creating a pull request?
> 
> I am thinking to install a Gentoo Prefix, snapshot its "vanilla"
> state, and run `emerge $mypackage` in the vanilla Prefix as a test.
> Are there better strategies?

There is a package to automate this, via docker:
dev-python/ebuildtester. For other methods, see
.

Kind regards, tastytea

-- 
Get my PGP key with `gpg --locate-keys tasty...@tastytea.de` or at
.


pgpOUlvDKmeNi.pgp
Description: Digitale Signatur von OpenPGP

Re: [gentoo-user] soft keyboard for touchscreen

[William Kenworthy]

Thanks,

    I needed to add to the start session for xfce4 - now its started
automaticly and connects to X when needed.

Thnaks for the hints I needed to track it down.

BillK



On 19/10/20 1:44 am, Mickaël Bucas wrote:
>
>
> Le dim. 18 oct. 2020 à 19:17, William Kenworthy  > a écrit :
>
> Thanks Mickaël,
>
>     I have onboard installed from an overlay (I have tried a
> couple of different ones, they seem to be variants of the same
> original package)
>
> How are you starting onboard? - the packages do not come with an
> initscript or hooks into X that I can see (though they seem to
> depend on systemd - I use openrc)
>
> BillK
>
> I start it manually, I've never thought about automating it :)
> On some systems I'm sometimes physically connected with a real
> keyboard and I don't need it in this situation.
>
> Best regards
> Mickaël Bucas
>
> On 19/10/20 12:46 am, Mickaël Bucas wrote:
>> Hi William
>>
>> Le dim. 18 oct. 2020 à 03:05, William Kenworthy
>> mailto:bi...@iinet.net.au>> a écrit :
>>
>> Can someone recommend a guide to installing a touch screen
>> aware soft
>> keyboard in gentoo?
>>
>> I have tried a number of keyboards but the various guides do
>> not say how
>> to integrate a soft keyboard in to a window manager (I am
>> using xfwm4
>> but could change) or login screen.
>>
>> I can manually start them, but they do not show up when an
>> editor,  text
>> box or login is required so I have to attach a physical
>> keyboard to
>> regain control.
>>
>>
>> BillK
>>  
>>
>>  
>> If you're using SDDM, you can activate the virtual keyboard with
>> the following line in the config file /etc/sddm.conf
>>
>> [General]
>> # Input method module
>> InputMethod=qtvirtualkeyboard
>>
>> For the session itself, under KDE on Ubuntu I use Onboard [1],
>> which is not available in Portage
>> I found a blog page [2] explaining how to install Onboard on
>> Gentoo, with an ebuild, but it's for Python 3.4 to 3.6
>> I've adapted the ebuild to Python 3.7 in my overlay [3] and it
>> worked as expected, either from another PC through VNC or from a
>> touch screen.
>> Onboard seems to originate from Gnome, and as I use it under KDE,
>> it should be independent from the window manager.
>>
>> Best regards
>> Mickaël Bucas
>>
>> [1] https://launchpad.net/onboard
>> [2]
>> 
>> https://fitzcarraldoblog.wordpress.com/2018/06/25/installing-the-onboard-on-screen-keyboard-in-gentoo-linux/
>> [3] https://github.com/mbucas/gentoo-overlay
>

Re: [gentoo-user] Strategies for testing an ebuild

[Steve Wilson]

I've had my own overlay for a while, maintaining my own versions of 
plex, new relic and even some removed packages that I use.
Until the the other day I was just making sure they install and work for 
myself, I have now discovered repoman and have several issues which 
actually need tidying up.
On top of this I store this in a private gitlab install so am now 
looking at CI/CD to automate the testing, but at this point I'm at the 
point of creating my own gentoo docker image with various things 
pre-installed to start serious check/test/install of new ebuilds.


Steve.

On 20/10/2020 19:01, Anton wrote:

Hi there,

I am taking on maintaining a package in gentoo-sci overlay. What are 
good ways to test that my ebuild works before creating a pull request?


I am thinking to install a Gentoo Prefix, snapshot its "vanilla" 
state, and run `emerge $mypackage` in the vanilla Prefix as a test. 
Are there better strategies?


Thanks,
Anton

Re: [gentoo-user] Strategies for testing an ebuild

[Jack]

On 2020.10.20 16:57, Alec Ten Harmsel wrote:

On Tue, Oct 20, 2020, at 14:01, Anton wrote:
> Hi there,
>
> I am taking on maintaining a package in gentoo-sci overlay. What are
> good ways to test that my ebuild works before creating a pull  
request?

>
> I am thinking to install a Gentoo Prefix, snapshot its "vanilla"  
state,
> and run `emerge $mypackage` in the vanilla Prefix as a test. Are  
there

> better strategies?

Generally, I just `sudo ebuild  clean  
install merge'
and test that it works directly on my system. I only proxy-maintain 1  
package,

though, so others will probably have much better workflows.

Alec


Using ebuild instead of emerge is probably not a sufficient test.  It  
does not check for dependencies, and I don't know what other subtle  
differences there are.  It's probably also good to run repoman on the  
ebuild.


Jack

Re: [gentoo-user] Strategies for testing an ebuild

[Alec Ten Harmsel]

On Tue, Oct 20, 2020, at 14:01, Anton wrote:
> Hi there,
> 
> I am taking on maintaining a package in gentoo-sci overlay. What are 
> good ways to test that my ebuild works before creating a pull request?
> 
> I am thinking to install a Gentoo Prefix, snapshot its "vanilla" state, 
> and run `emerge $mypackage` in the vanilla Prefix as a test. Are there 
> better strategies?

Generally, I just `sudo ebuild  clean install merge'
and test that it works directly on my system. I only proxy-maintain 1 package,
though, so others will probably have much better workflows.

Alec

[gentoo-user] Strategies for testing an ebuild

[Anton]

Hi there,

I am taking on maintaining a package in gentoo-sci overlay. What are 
good ways to test that my ebuild works before creating a pull request?


I am thinking to install a Gentoo Prefix, snapshot its "vanilla" state, 
and run `emerge $mypackage` in the vanilla Prefix as a test. Are there 
better strategies?


Thanks,
Anton

Re: [gentoo-user] No sound. Please, help!

[Dale]

gevisz wrote:
> пн, 19 окт. 2020 г. в 18:13, Dale :
>> gevisz wrote:
>>> пн, 19 окт. 2020 г. в 02:18, Dale :
 On the modules or in kernel, I compile all mine in the kernel.  The only
 modules I have is my nvidia video drivers. There's pro's and con's to
 each so whatever works and you like.
>>> I actually asked a question not about the choice between "in kernel"
>>> or "as a module" but about "to build or not to build" at all. :)
>>>
>>> So, once more: Is it better to compile the driver for my HDMI audio
>>> device or not, if I am not going to use HDMI audio output?
>>>
>> Ahh.  Well, if you build it and then need it later, it's already there.
>> If you don't and then need it later, you have to go back and build it
>> and may be in a hurry.  I tend to get all hardware working even if I'm
>> not using it at the time.
> I have just thought that it may be better if the kernel knows how to
> deal with this piece of hardware even if it is not going to use it.

True.  It may improve how the hardware works.  One could test the
theory.  One could wait until the next kernel build to do it too.  Lots
of options there.  ;-)


 Glad it's working now.  I need a shower.  I been cutting down trees and
 dragging them to a pile to rot or burn.  I'm tired, I stink which
 requires a shower and I'm hungry.  Cutting and getting rid of a 24 inch
 across tree isn't easy when you have a 20 inch bar on the chainsaw.  :/
>>> Thank you once more. And you should not rush to answer: my initial
>>> intention was to finally solve this problem till the end of this
>>> month, and now it is solved during only one weekend. :)
>>>
>>>
>>
>> Well, when on this mailing list, you will get ideas pretty fast.  Given
>> that you had things working but not making noise, my first thought was
>> the mute.  I ran into that a couple times myself in the past.  One would
>> think it would default to a low level but something you can hear.  I
>> guess tho they think you should be forced to adjust the mixers and other
>> sound control settings so that you can enable/leave disabled to your
>> liking.  It's 6 of one or half a dozen of the other I guess.  ;-)
>>
>> Back to cutting trees.  Got my insect spray on today tho.  Things sound
>> like large helicopters flying around out there.  O-o
> Maybe, it makes sense to find an easier job? :)
>
>


I'm doing that on my place here.  Trying to make things better.  It's a
hard job and I'm amazed I have done as much as I have.  I'm about done
cleaning up what I started but I may not cut any more this year.  I can
tell my old joints are starting to get upset. 

Did get some firewood for a friend out of it tho. 

Dale

:-)  :-) 

Re: [gentoo-user] No sound. Please, help!

[gevisz]

пн, 19 окт. 2020 г. в 18:13, Dale :
>
> gevisz wrote:
> > пн, 19 окт. 2020 г. в 02:18, Dale :
> >> On the modules or in kernel, I compile all mine in the kernel.  The only
> >> modules I have is my nvidia video drivers. There's pro's and con's to
> >> each so whatever works and you like.
> >
> > I actually asked a question not about the choice between "in kernel"
> > or "as a module" but about "to build or not to build" at all. :)
> >
> > So, once more: Is it better to compile the driver for my HDMI audio
> > device or not, if I am not going to use HDMI audio output?
> >
>
> Ahh.  Well, if you build it and then need it later, it's already there.
> If you don't and then need it later, you have to go back and build it
> and may be in a hurry.  I tend to get all hardware working even if I'm
> not using it at the time.

I have just thought that it may be better if the kernel knows how to
deal with this piece of hardware even if it is not going to use it.

> >> Glad it's working now.  I need a shower.  I been cutting down trees and
> >> dragging them to a pile to rot or burn.  I'm tired, I stink which
> >> requires a shower and I'm hungry.  Cutting and getting rid of a 24 inch
> >> across tree isn't easy when you have a 20 inch bar on the chainsaw.  :/
> > Thank you once more. And you should not rush to answer: my initial
> > intention was to finally solve this problem till the end of this
> > month, and now it is solved during only one weekend. :)
> >
> >
>
>
> Well, when on this mailing list, you will get ideas pretty fast.  Given
> that you had things working but not making noise, my first thought was
> the mute.  I ran into that a couple times myself in the past.  One would
> think it would default to a low level but something you can hear.  I
> guess tho they think you should be forced to adjust the mixers and other
> sound control settings so that you can enable/leave disabled to your
> liking.  It's 6 of one or half a dozen of the other I guess.  ;-)
>
> Back to cutting trees.  Got my insect spray on today tho.  Things sound
> like large helicopters flying around out there.  O-o

Maybe, it makes sense to find an easier job? :)

Re: [gentoo-user] UEFI booting again - FIXED

[Peter Humphrey]

On Monday, 19 October 2020 18:08:53 -00 Michael wrote:

> However, I don't think anyone would argue against empirical repeatable
> outcomes.  :-)

:)

-- 
Regards,
Peter.