Skip to Content.
Sympa Menu

sm-commit - Re: [SM-Commit] GIT changes to master grimoire by Ismael Luceno (ebb3d4ea0344f74a552a75a2b3f4df78275aa44c)

sm-commit AT lists.ibiblio.org

Subject: Source Mage code commit list

List archive

Chronological Thread  
  • From: Ismael Luceno <ismael.luceno AT gmail.com>
  • To: Thomas Orgis <thomas-forum AT orgis.org>
  • Cc: sm-commit AT lists.ibiblio.org
  • Subject: Re: [SM-Commit] GIT changes to master grimoire by Ismael Luceno (ebb3d4ea0344f74a552a75a2b3f4df78275aa44c)
  • Date: Wed, 24 Aug 2016 21:22:56 -0300

On 15/Aug/2016 23:43, Thomas Orgis wrote:
> Am Mon, 15 Aug 2016 15:30:31 -0300
> schrieb Ismael Luceno <ismael.luceno AT gmail.com>:
> > Headers we would want:
> > * X-Patch-Strip (default = 1)
> > * X-Patch-Label (a shorthand, mandatory for optional patches)
> > * X-Patch-Deps (list of shorthands)
> > * X-Patch-Conflict (list of shorthands)
>
> I'd rather have such in a declarative-like syntax in the PRE_BUILD … or
> a PATCHES file, very much like DEPENDS. Separate data (patches) and
> metadata (dependency information). That way, one also could group
> patches together for logical features etc. Not sure how the indivudual
> labels would work there.

OK, if it's not in the patches themselves, I would prefer a PATCHES
file, as it would make more explicit the info is processed in CONFIGURE
and PRE_BUILD.

After much thinking, perhaps there are a few scenarios where this is
more flexible.

The question now is: should this be part of Sorcery itself?




Archive powered by MHonArc 2.6.24.

Top of Page