Hi, On Mon, Feb 11, 2019 at 02:06:19PM +0100, Marc-André Lureau wrote: > Hi > > On Mon, Feb 11, 2019 at 1:59 PM Victor Toso <victortoso@xxxxxxxxxx> wrote: > > > > Hi, > > > > On Mon, Feb 11, 2019 at 01:09:41PM +0100, Marc-André Lureau wrote: > > > > Having a virt-viewer flatpak does not mean _not_ having a > > > > spicy.flatkpak (to me); one is full featured spice client while > > > > the other a testing tool... > > > > > > It looks like a lot of duplication of flatpak effort. Maybe you could > > > simply ship spicy in virt-viewer flatpak, so it could be run from > > > command line (please no .desktop) > > > > Is the fact that we are installing a .desktop for spicy the only > > issue here or you don't want to see a flatpak of spicy in the > > gitlab-ci anyway? (btw, I'm not planning to upload this to any > > flatpak provider). > > What's the point in building a spice-gtk flatpak then, when you > have virt-viewer flatpak? You replied my question with another question. My main motivation is that spicy is self contained in spice-gtk, smaller and targeted to be a testing tool, so, testing spice-gtk changes. If I add virt-viewer -> flatpak or msi installer to gitlab-ci's artifacts, that's out of scope of spice-gtk although I'll be using it all the time...
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ Spice-devel mailing list Spice-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/spice-devel