git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v2 1/1] ci(osx): use new location of the `perforce` cask

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 22, 2019, 23:37 UTC
Message-ID
<xmqq36fkl5bd.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<nycvar.QRO.7.76.6.1910230123540.46@tvgsbejvaqbjf.bet>
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
Show 9 quoted lines
>> This is already in 'next' X-<; reverting a merge is cheap but I
>> prefer to do so when we already have a replacement.
>
> I force-pushed (see https://github.com/gitgitgadget/git/pull/400), and
> once Stolee approves, he will submit v3. This will only change the
> commit message, though, as I disagree that hard-coding the URL would be
> an improvement: the nice thing about a package management system is that
> the user does not need to know the details (or need to know if the
> details change, like, ever).

If this were meant for the upcoming release, I would rather see us copy a butt-ugly-but-known-working procedure if we have one this close to -rc1. If the hard-coded URL ever changes, the procedure we would be copying from would be broken anyway.

But I agree 100% that we should take a conceptually cleaner approach for the longer term. Let's replace the original one with this and cook in 'next'---it would be ideal if the ugly-but-know-working one be updated to match in the meantime, but if it is bypassing package management for a reason (the upstream just publishes the URL to download from without packaging it properly, for example?), that would not be possible, and it is OK if that is the case.

Thanks.
Previous: Johannes SchindelinNext: Johannes Schindelin
Message 9 of 24 in “ci: update caskroom/cask/perforce to new location”
  1. 0/1 ci: update caskroom/cask/perforce to new locationDerrick Stolee via GitGitGadget, Oct 15, 2019
  2. 1/1 ci(osx): use new location of the `perforce` caskJohannes Schindelin via GitGitGadget, Oct 15, 2019
  3. Johannes SchindelinOct 17, 2019
  4. 0/1 ci: update caskroom/cask/perforce to new locationDerrick Stolee via GitGitGadget, Oct 17, 2019
  5. 1/1 ci(osx): use new location of the `perforce` caskJohannes Schindelin via GitGitGadget, Oct 17, 2019
  6. SZEDER GáborOct 18, 2019
  7. Junio C HamanoOct 21, 2019
  8. Johannes SchindelinOct 22, 2019
  9. Junio C HamanoOct 22, 2019
  10. Johannes SchindelinOct 22, 2019
  11. SZEDER GáborOct 23, 2019
  12. 0/1 ci: update caskroom/cask/perforce to new locationDerrick Stolee via GitGitGadget, Oct 23, 2019
  13. 1/1 ci(osx): use new location of the `perforce` caskJohannes Schindelin via GitGitGadget, Oct 23, 2019
  14. Junio C HamanoOct 23, 2019
  15. SZEDER GáborOct 23, 2019
  16. ci: fix GCC install in the Travis CI GCC OSX jobSZEDER Gábor, Oct 24, 2019
  17. SZEDER GáborNov 18, 2019
  18. Johannes SchindelinNov 19, 2019
  19. Junio C HamanoNov 20, 2019
  20. Johannes SchindelinNov 20, 2019
  21. Junio C HamanoNov 20, 2019
  22. SZEDER GáborNov 20, 2019
  23. Junio C HamanoNov 21, 2019
  24. Johannes SchindelinNov 21, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.