On 03/04/2018 07:13 PM, Damjan Georgievski via arch-general wrote:
>>> This means that PKGBUILDs which checkout a specific revision are
>>> actually worse than the rest, as you cannot even get the source without
>>> knowing how many commits you need (rather than failing afterwards in
>>> pkgver() o
>> This means that PKGBUILDs which checkout a specific revision are
>> actually worse than the rest, as you cannot even get the source without
>> knowing how many commits you need (rather than failing afterwards in
>> pkgver() or something).
>
> Right. I had assumed that git clone -b/--branch did a
On 3/4/18, Eli Schwartz wrote:
> On 03/04/2018 03:27 PM, Carsten Mattner wrote:
>> Interesting. What does PKGBUILD do with history of more than 10
>> revisions?
>> If we checkout a tag or specific commit (e.g. xf86-video-intel), what
>> does PKGBUILD need prior revisions for? I'm sure you're corre
On 03/04/2018 03:27 PM, Carsten Mattner wrote:
> Interesting. What does PKGBUILD do with history of more than 10 revisions?
> If we checkout a tag or specific commit (e.g. xf86-video-intel), what
> does PKGBUILD need prior revisions for? I'm sure you're correct, I'd
> like to know what it is, if yo
On 3/4/18, Eli Schwartz wrote:
> On 03/04/2018 10:58 AM, Carsten Mattner wrote:
>> At least for GitHub remotes, don't they still support checking out
>> with SVN? If they do, this would be faster and use less space, too,
>> when we just need a certain revision and no history at all.
>>
>> Other th
Am 04.03.2018 um 17:05 schrieb Eli Schwartz via arch-general:
> The point, is that PKGBUILDs do look for history, and make use of it --
> figuring out clever ways to avoid pulling history is completely missing
> the point that we, well, want history.
But the history is only needed for the default
On 03/04/2018 10:58 AM, Carsten Mattner wrote:
> At least for GitHub remotes, don't they still support checking out
> with SVN? If they do, this would be faster and use less space, too,
> when we just need a certain revision and no history at all.
>
> Other than that, I'm "pretty sure" that a git
At least for GitHub remotes, don't they still support checking out
with SVN? If they do, this would be faster and use less space, too,
when we just need a certain revision and no history at all.
Other than that, I'm "pretty sure" that a git depth of 10 commits
will work for most repositories when
On 03/04/2018 10:37 AM, ProgAndy wrote:
> Maybe a working option would be to implement fragmant variables for some
> git options like depth, shallow-exclude and shallow-since, but that is
> likely not trivial.
>
> source=("one::git+https://repo.git#branch=master:shallow-exclude=v4.14";
> "two::git
Am 04.03.2018 um 01:08 schrieb Eli Schwartz via arch-general:
Yep -- more or less this. There is no way for git to fetch "all commits
since a given tag", and obviously `git describe` which is used in the
standard pkgver() function cannot describe the remote repository... not
to mention what happe
On 2018-03-04 13:50, Guus Snijders via arch-general wrote:
Just out of curiosity; could you try deleting the symlink and LD_preloading
/usr/lib/libtifinfo.so.5 ?
The current replies on the ML are a technically correct, though a bit blunt.
If the preload tricks actually works, we could advice t
Op vr 2 mrt. 2018 12:18 schreef Alajos Odoyle :
> On 2018-03-02 11:38, Dan Haworth wrote:
> >
> > I had the same issue, seems to be related to the following bug
> > https://github.com/mono/mono/issues/6752. I downgraded ncurses to 6.0 to
> > get things going again.
> >
> > --dan
>
> Thanks, that w
12 matches
Mail list logo
