4 ms·

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

by laruss5 11d ago

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.

TimWolla 11d ago
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] https://packagist.org/packages/jakeasmith/http_build_url https://packagist.org/packages/jakeasmith/http_build_url
- Timwi 11d ago
  It would have been nice if a replacement had been suggested.
  - 0x073 11d ago
    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.
  - pmlnr 11d ago
    Read the linked entry.