Thread

1. laruss5 · 1789629838 · focus · HN ↗

   For a package with that kind of install base, is there a final release that prints the migration options in a deprecation notice? People will find it years from now through old Stack Overflow answers.

   1. TimWolla · 1789630147 · focus · HN ↗

      The package is marked as abandoned on Packagist [1]

      > This package is abandoned and no longer maintained. No replacement package was suggested.

      Both adding it as a dependency using composer and installing it from a lockfile results in:

          $ composer require jakeasmith/http_build_url
          […]
          Package jakeasmith/http_build_url is abandoned, you should avoid using it. No replacement was suggested.
          […]
          $ rm -r vendor/
          $ composer install
          […]
            - Installing jakeasmith/http_build_url (1.0.2): Extracting archive
          Package jakeasmith/http_build_url is abandoned, you should avoid using it. No replacement was suggested.
          […]
      

      [1] <a href="https:&#x2F;&#x2F;packagist.org&#x2F;packages&#x2F;jakeasmith&#x2F;http_build_url" rel="nofollow">https:&#x2F;&#x2F;packagist.org&#x2F;packages&#x2F;jakeasmith&#x2F;http_build_url

      1. Timwi · 1789642982 · focus · HN ↗

         It would have been nice if a replacement had been suggested.

         1. 0x073 · 1789645431 · focus · HN ↗

            Replacement is defined in the github repo, in composer you can only define an replacement package, but there is no real replacement, just alternative ways.

Unofficial Hacker News client; not affiliated with Y Combinator.