New releases for bugfixes

samuel ammonius sfammonius at gmail.com
Thu Sep 8 19:50:51 BST 2022


Bug fixes don't change the entire package, only the executable, so
why can't apps just be programmed to update themselves? There
could be precompiled binaries stored on the git repos of each project
for a few CPU architectures, or maybe the app could even recompile
itself inside /tmp since most systems KDE runs on come with a compiler
by default (and macros could also be stored so that apps have the
same configuration throughout updates).

Cheers,
Sam

On Thu, Sep 8, 2022 at 11:58 AM Heiko Becker <heiko.becker at kde.org> wrote:

> On Thursday, 8 September 2022 13:59:43 CEST, Ahmad Samir wrote:
> > From the git-archive manual page:
> >
> > «git archive behaves differently when given a tree ID versus
> > when given a commit ID or tag ID. In the first case the current
> > time is used as the modification time of each file in the
> > archive. In the latter case the commit time as recorded in the
> > referenced commit object is used instead. Additionally the
> > commit ID is stored in a global extended pax header if the tar
> > format is used; it can be extracted using git get-tar-commit-id.
> > In ZIP files it is stored as a file comment.»
>
> Before anybody tries that *now*, at least for Gear the tarballs are
> currently created with git archive --remote=kde:$repo $branch ..
> So they currently won't have that information.
>
> Regards,
> Heiko
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-devel/attachments/20220908/bdad2c7e/attachment.htm>


More information about the kde-devel mailing list