Hi,
I got an archive (???) of an Linux application, which
has the extension "*.AppImage".
What is that?
Is it possible to "unpack" that into something more common?
How to handle that?
Thanks a lot for any help in advance!
Cheers
Meino
On Sun, Nov 5, 2017 at 6:20 AM, wrote:
>
> I got an archive (???) of an Linux application, which
> has the extension "*.AppImage".
>
> What is that?
>
> Is it possible to "unpack" that into something more common?
> How to handle that?
Does it use this spec?
https://appimage.org/
Hi,
Since cura/curaengine (portage) does not compile on my system and is
relatively old I downloaded cura for Linux from www.ultimaker.com.
This runs on my system without the installation of addtional
applications/libraries.
Unfortunately the font rendering screwed up and makes menu entries,
tex
On 11/05 06:29, Tom H wrote:
> On Sun, Nov 5, 2017 at 6:20 AM, wrote:
> >
> > I got an archive (???) of an Linux application, which
> > has the extension "*.AppImage".
> >
> > What is that?
> >
> > Is it possible to "unpack" that into something more common?
> > How to handle that?
>
> Does it us
On Sun, Nov 5, 2017 at 7:11 AM, wrote:
> On 11/05 06:29, Tom H wrote:
>> On Sun, Nov 5, 2017 at 6:20 AM, wrote:
>>>
>>> I got an archive (???) of an Linux application, which
>>> has the extension "*.AppImage".
>>>
>>> What is that?
>>>
>>> Is it possible to "unpack" that into something more commo
On Saturday, 4 November 2017 19:23:40 GMT Rich Freeman wrote:
> On Sat, Nov 4, 2017 at 2:17 PM, Nikos Chantziaras wrote:
> > On 04/11/17 18:15, siefke_lis...@web.de wrote:
> >> I have a short question to systemd. I would like to ask your experience
> >> in the changeover. Was it easy? Were there p
On 11/05 07:21, Tom H wrote:
> On Sun, Nov 5, 2017 at 7:11 AM, wrote:
> > On 11/05 06:29, Tom H wrote:
> >> On Sun, Nov 5, 2017 at 6:20 AM, wrote:
> >>>
> >>> I got an archive (???) of an Linux application, which
> >>> has the extension "*.AppImage".
> >>>
> >>> What is that?
> >>>
> >>> Is it po
On 2017-11-04 18:42, Ian Zimmerman wrote:
On 2017-11-04 01:39, Kai Peter wrote:
> If you want to run a monthly job on a host that is not always on, do
> you have to pretend it's an hourly job and check in the script
> itself?
This is a special case to me. IMHO special cases
On 05/11/2017 16:28, Kai Peter wrote:
>
>
> On 2017-11-04 18:42, Ian Zimmerman wrote:
>
>> On 2017-11-04 01:39, Kai Peter wrote:
>
>>
>
>>> > If you want to run a monthly job on a host that is not always on, do
>
>>> > you have to pretend it's an hourly job and check in the script
>
>>> > it
On 05/11/2017 15:48, tu...@posteo.de wrote:
> On 11/05 07:21, Tom H wrote:
>> On Sun, Nov 5, 2017 at 7:11 AM, wrote:
>>> On 11/05 06:29, Tom H wrote:
On Sun, Nov 5, 2017 at 6:20 AM, wrote:
>
> I got an archive (???) of an Linux application, which
> has the extension "*.AppImage".
On 11/05 04:46, Alan McKinnon wrote:
> On 05/11/2017 15:48, tu...@posteo.de wrote:
> > On 11/05 07:21, Tom H wrote:
> >> On Sun, Nov 5, 2017 at 7:11 AM, wrote:
> >>> On 11/05 06:29, Tom H wrote:
> On Sun, Nov 5, 2017 at 6:20 AM, wrote:
> >
> > I got an archive (???) of an Linux appli
On Sun, Nov 5, 2017 at 6:43 AM, Alan McKinnon wrote:
>
> There are other schedulers out there that succeed where cron fails (eg
> Control-M, chronos, quartz), but those are all large, bulky, designed
> for big complex installs/requirements and probably not suited for simple
> things you'd deploy o
On Sun, Nov 5, 2017 at 6:46 AM, Alan McKinnon wrote:
> On 05/11/2017 15:48, tu...@posteo.de wrote:
>>
>> unpacking is not implemented yet.
>
>
> Reading only this thread, it looks like an upstream used a horribly
> incomplete scheme for distribution that isn't even ready for launch.
>
> And yet th
On 11/05 04:04, tu...@posteo.de wrote:
> On 11/05 04:46, Alan McKinnon wrote:
> > On 05/11/2017 15:48, tu...@posteo.de wrote:
> > > On 11/05 07:21, Tom H wrote:
> > >> On Sun, Nov 5, 2017 at 7:11 AM, wrote:
> > >>> On 11/05 06:29, Tom H wrote:
> > On Sun, Nov 5, 2017 at 6:20 AM, wrote:
> > >
On Sun, 5 Nov 2017 16:46:07 +0200
> Reading only this thread, it looks like an upstream used a horribly
> incomplete scheme for distribution that isn't even ready for launch.
What, like KDE-4, KDE-plasma, ... ?
--
Regards,
Peter.
On 2017-11-05 07:11, Rich Freeman wrote:
> But, I agree that it makes far more sense to just have desktop users
> use an appropriate cron implementation designed to handle the machine
> being off most of the time vs trying to use shell scripting to make
> vixie cron into such an implementation.
>
There are other schedulers out there that succeed where cron fails (eg
Control-M, chronos, quartz), but those are all large, bulky, designed
for big complex installs/requirements and probably not suited for
simple
things you'd deploy out of a base in portage
Long time ag
On Sun, 05 Nov 2017 17:56:56 +0100, Kai Peter wrote:
> OT: Seems that since the last update of my MUA the formatting of my
>
> mails is broken - at least at reply's. There are extra line breaks.
>
> G - if you not do everything by yourself ... ;-)
... at least you have someone else to b
On 2017-11-05 18:12, Neil Bothwick wrote:
On Sun, 05 Nov 2017 17:56:56 +0100, Kai Peter wrote:
OT: Seems that since the last update of my MUA the formatting of my
mails is broken - at least at reply's. There are extra line breaks.
G - if you not do everything by yourse
On Sun, Nov 5, 2017 at 8:10 AM, Ian Zimmerman wrote:
> On 2017-11-05 07:11, Rich Freeman wrote:
>
>> But, I agree that it makes far more sense to just have desktop users
>> use an appropriate cron implementation designed to handle the machine
>> being off most of the time vs trying to use shell sc
On 05/11/2017 17:11, Rich Freeman wrote:
> On Sun, Nov 5, 2017 at 6:43 AM, Alan McKinnon wrote:
>>
>> There are other schedulers out there that succeed where cron fails (eg
>> Control-M, chronos, quartz), but those are all large, bulky, designed
>> for big complex installs/requirements and probabl
On 2017-11-05 14:22, Rich Freeman wrote:
> Second, my actual objection is more to sticking wrappers around an
> upstream program just to extend its capabilities, when other software
> is maintained upstream that already does what you're re-inventing.
> When you already have 47 different cron imple
On 2017-11-05 21:40, Alan McKinnon wrote:
> Agreed again. My desktop cronjobs are all empty and when I had some
> they were of the "do this once a week or once a day" variety. I didn't
> care when they ran, just that they did every so often
What about the synchronization and predictability aspect
On Sun, Nov 5, 2017 at 4:40 PM, Ian Zimmerman wrote:
> On 2017-11-05 14:22, Rich Freeman wrote:
>
>> Second, my actual objection is more to sticking wrappers around an
>> upstream program just to extend its capabilities, when other software
>> is maintained upstream that already does what you're r
Further to the thread re mysterious behaviour of 'sane-backends',
I remembered what happened when I set my new scanner up earlier in 2017.
There is no driver in 'sane-backends', because it contains a binary blob.
You have to download an appropriate pkg for the V550 from Epson,
which provides insta
25 matches
Mail list logo
