Changes between Version 6 and Version 7 of Ticket #13186, comment 12


Ignore:
Timestamp:
Mar 21, 2025, 1:20:12 PM (3 weeks ago)
Author:
Robin Candau

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #13186, comment 12

    v6 v7  
    1919Both types of package managers actually implies to fetch files from upstream. The only difference between the first and the second type in that regard is that, in the fist type, a package maintainer does the fetching once beforehand (and also compiles the software) so users don't have to do it themselves (as compared to the second type where users execute the recipe themselves locally, which includes fetching files from upstream).
    2020
    21 This file fetching from upstream, whether it is done by package maintainers in type 1 or users in type 2, is automated as part of the packaging process when packaging a new release. Our packaging tooling automatically fetches files from upstream according to the source declared in our build recipes.
     21Fetching files from upstream, whether it is done by package maintainers in type 1 or users in type 2, is automated as part of the packaging process when packaging a new release. Our packaging tooling automatically fetches files from upstream according to the source URL declared in our build recipes.
    2222
    23 Since the URL to download filezilla & libfilezilla sources became "unstable", this is of course not possible for our tooling to download them automatically anymore (as the random part of the download URL cannot be "fixed" / predicted, obviously).
    24 Therefore, the initial upstream source downloading required to fetch (and store) the sources now became an additional manual step (whether it is for package maintainers in type 1 and users in type 2). Aside from that, it also breaks our automated packaging workflow for our filezilla related packages, which makes them way more painful to maintain now.
     23Since the URL to download filezilla & libfilezilla sources became "unstable", this is of course not possible for our tooling to download them anymore (as the random part of the download URL cannot be "fixed" / predicted, obviously).
     24Therefore, the initial upstream sources downloading, required to fetch (and store) the sources, now became an additional manual step (whether it is for package maintainers in type 1 and users in type 2). This breaks our automated packaging workflow for filezilla related packages, making them way more painful to maintain now.
    2525
    2626> They are offering their services without actually wanting to bear the costs of providing such service in terms of traffic, server hosting and maintenance costs. In short: 'Leeching'.