* git repo vs archive for source
@ 2020-10-23 21:56 Joe Slater
2020-10-23 22:17 ` [OE-core] " Andrei Gherzan
0 siblings, 1 reply; 3+ messages in thread
From: Joe Slater @ 2020-10-23 21:56 UTC (permalink / raw)
To: 'openembedded-core@lists.openembedded.org'
[-- Attachment #1: Type: text/plain, Size: 171 bytes --]
When updating versions, like for ruby, say, is it desirable to switch from using "released" archives to using the git(hub) repo with the corresponding branch/tag?
Joe
[-- Attachment #2: Type: text/html, Size: 1700 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [OE-core] git repo vs archive for source
2020-10-23 21:56 git repo vs archive for source Joe Slater
@ 2020-10-23 22:17 ` Andrei Gherzan
2020-10-23 23:58 ` Joshua Watt
0 siblings, 1 reply; 3+ messages in thread
From: Andrei Gherzan @ 2020-10-23 22:17 UTC (permalink / raw)
To: Joe Slater; +Cc: 'openembedded-core@lists.openembedded.org'
[-- Attachment #1: Type: text/plain, Size: 455 bytes --]
23 Oct 2020 22:56:28 Joe Slater <joe.slater@windriver.com>:
> When updating versions, like for ruby, say, is it desirable to switch from using “released” archives to using the git(hub) repo with the corresponding branch/tag?
I think git is usually the preferred way mainly because it matches code directly as opposed to a packaged payload.
The exception that I found is when people are using git to store binaries.
--
Andrei Gherzan
[-- Attachment #2: Type: text/html, Size: 926 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [OE-core] git repo vs archive for source
2020-10-23 22:17 ` [OE-core] " Andrei Gherzan
@ 2020-10-23 23:58 ` Joshua Watt
0 siblings, 0 replies; 3+ messages in thread
From: Joshua Watt @ 2020-10-23 23:58 UTC (permalink / raw)
To: Andrei Gherzan; +Cc: Joe Slater, OE-core
[-- Attachment #1: Type: text/plain, Size: 807 bytes --]
On Fri, Oct 23, 2020, 5:17 PM Andrei Gherzan <andrei@gherzan.ro> wrote:
>
> 23 Oct 2020 22:56:28 Joe Slater <joe.slater@windriver.com>:
>
> > When updating versions, like for ruby, say, is it desirable to switch
> from using “released” archives to using the git(hub) repo with the
> corresponding branch/tag?
>
> I think git is usually the preferred way mainly because it matches code
> directly as opposed to a packaged payload.
>
> The exception that I found is when people are using git to store binaries.
>
Right. You don't want to use the archives that github creates automatically
because the checksums are not stable and they can change over time. If some
one is manually attaching an archive to a release, that's usually ok to use
> --
>
> Andrei Gherzan
>
>
>
>
[-- Attachment #2: Type: text/html, Size: 1824 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2020-10-23 23:59 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2020-10-23 21:56 git repo vs archive for source Joe Slater
2020-10-23 22:17 ` [OE-core] " Andrei Gherzan
2020-10-23 23:58 ` Joshua Watt
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox