Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.maint.python > #15681

Re: Uscan: watch and changelog

From Soren Stoutner <soren@debian.org>
Newsgroups linux.debian.maint.python
Subject Re: Uscan: watch and changelog
Date 2024-03-29 19:30 +0100
Message-ID <Inp9f-2A8j-27@gated-at.bofh.it> (permalink)
References <Inp9f-2A8j-29@gated-at.bofh.it> <Inl5D-2xCL-3@gated-at.bofh.it> <InnTQ-2zs0-5@gated-at.bofh.it> <Ino3v-2zvm-9@gated-at.bofh.it>
Organization Debian

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

On Friday, March 29, 2024 10:16:56 AM MST c.buhtz@posteo.jp wrote:
> There is no "opts=". So again. Why would you suggest to use "opts="? I want 
to
> learn. I don't want to fight.

One of the interesting things about uscan is there are often multiple different 
ways to connect to an upstream source and get what you want out of it.

So, for example, if upstream posts tarballs, you can scan the HTML for those 
and find one that matches the latest version number in the changelog (or one 
with a newer version number, which uscan can use to notify you an update is 
available).

However, uscan also speaks git.  If you use `opts=git`, then instead of 
scanning the HTML looking for a tarball, it connects through git and looks at 
the tags to find a suitable release.  It then clones that commit and uses the 
source to produce a tarball.

Some upstream repositories both produce release tarballs and tag their 
releases in git, so either approach would work.  Some only do one or the 
other.

-- 
Soren Stoutner
soren@debian.org

Back to linux.debian.maint.python | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Uscan: watch and changelog <c.buhtz@posteo.jp> - 2024-03-29 15:10 +0100
  Re: Uscan: watch and changelog Andrey Rakhmatullin <wrar@debian.org> - 2024-03-29 15:30 +0100
  Re: Uscan: watch and changelog Andrey Rakhmatullin <wrar@debian.org> - 2024-03-29 15:30 +0100
  Re: Uscan: watch and changelog Andrey Rakhmatullin <wrar@debian.org> - 2024-03-29 15:30 +0100
    Re: Uscan: watch and changelog <c.buhtz@posteo.jp> - 2024-03-29 17:40 +0100
  Re: Uscan: watch and changelog Carsten Schoenert <c.schoenert@t-online.de> - 2024-03-29 16:30 +0100
    Re: Uscan: watch and changelog <c.buhtz@posteo.jp> - 2024-03-29 17:40 +0100
      Re: Uscan: watch and changelog Carsten Schoenert <c.schoenert@t-online.de> - 2024-03-29 18:10 +0100
        Re: Uscan: watch and changelog <c.buhtz@posteo.jp> - 2024-03-29 18:20 +0100
          Re: Uscan: watch and changelog Soren Stoutner <soren@debian.org> - 2024-03-29 19:30 +0100
            Re: Uscan: watch and changelog <c.buhtz@posteo.jp> - 2024-03-29 21:20 +0100
              Re: Uscan: watch and changelog Soren Stoutner <soren@debian.org> - 2024-03-29 21:50 +0100
                Re: Uscan: watch and changelog <c.buhtz@posteo.jp> - 2024-03-31 15:40 +0200
                Re: Uscan: watch and changelog Michael Stehmann <michael@canzeley.de> - 2024-03-31 16:20 +0200
                Re: Uscan: watch and changelog Paul Boddie <paul@boddie.org.uk> - 2024-03-31 17:20 +0200
                Re: Uscan: watch and changelog <c.buhtz@posteo.jp> - 2024-04-06 09:50 +0200
      Re: Uscan: watch and changelog Paul Boddie <paul@boddie.org.uk> - 2024-03-29 18:20 +0100

csiph-web