ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: Henning Hraban Ramm via ntg-context <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@freedom.nl>
Subject: Re: [NTG-context] new module installer and .tar.gz compression
Date: Tue, 9 May 2023 08:06:22 +0200	[thread overview]
Message-ID: <1bb132b8-d806-ee6d-90f7-c5813d3b236c@freedom.nl> (raw)
In-Reply-To: <22e10763-2188-403d-3803-8979235da50b@fiee.net>

On 5/9/2023 7:17 AM, Henning Hraban Ramm via ntg-context wrote:
> Am 09.05.23 um 01:19 schrieb Hans Hagen via ntg-context:
>> On 5/8/2023 8:55 PM, Henning Hraban Ramm via ntg-context wrote:
>>
>>> But either the module scripts should re-pack tgz archives or the 
>>> installer must learn to handle them.
> 
>> The script now
>>
>> -- before installing uninstalls a previous installation
>> -- can uninstall an installed module
>> -- can list installed modules
> 
> Great!
> 
>> For the moment I disable a few badly packages zips:
>>
>> metaducks, sudoku, aquamints, simpleslides
>>
>> as they put files in the root and their own directories and I am not 
>> adding a zip-root remover and additional checkers.
> 
> I regard it good practice to have README, LICENSE and VERSION files in 
> the root. A public git repository without these is incomplete, and if we 
> use the zip/tgz packaging of platforms like github or gitea (codeberg), 
> we can’t exclude them.
> The installer script could just ignore/delete them.
I currently wipe them but it's extra work and who knows what shows up in 
the future.

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : https://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2023-05-09  6:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-08 15:20 Pablo Rodriguez via ntg-context
2023-05-08 15:58 ` Bruce Horrocks via ntg-context
2023-05-08 17:40   ` Pablo Rodriguez via ntg-context
2023-05-08 18:55     ` Henning Hraban Ramm via ntg-context
2023-05-08 22:33       ` Hans Hagen via ntg-context
2023-05-08 23:19       ` Hans Hagen via ntg-context
2023-05-09  5:17         ` Henning Hraban Ramm via ntg-context
2023-05-09  6:06           ` Hans Hagen via ntg-context [this message]
2023-05-09  7:30         ` Hans van der Meer via ntg-context
2023-05-09  7:43           ` Hans Hagen via ntg-context

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1bb132b8-d806-ee6d-90f7-c5813d3b236c@freedom.nl \
    --to=ntg-context@ntg.nl \
    --cc=j.hagen@freedom.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).