Hi,
This patch adds a new PKGBUILD variable, changelog, which replaces the old,
hardcoded ChangeLog file. The old behavior is completely removed, which means
that existing ChangeLog files will be ignored if there is no appropriate line
in the PKGBUILD. For a more detailed description, please se
On Thu, Oct 8, 2009 at 9:10 AM, Cedric Staniewski wrote:
> Hi,
>
> This patch adds a new PKGBUILD variable, changelog, which replaces the old,
> hardcoded ChangeLog file. The old behavior is completely removed, which means
> that existing ChangeLog files will be ignored if there is no appropriat
On Sat, Oct 10, 2009 at 4:34 PM, Dan McGee wrote:
> On Thu, Oct 8, 2009 at 9:10 AM, Cedric Staniewski wrote:
>> Hi,
>>
>> This patch adds a new PKGBUILD variable, changelog, which replaces the old,
>> hardcoded ChangeLog file. The old behavior is completely removed, which
>> means that existing
On Sat, Oct 10, 2009 at 4:37 PM, Xavier wrote:
>
> This looked good to me.
>
Sorry for the double mail.
I just had one question :
Will every package maintainer figure out easily that his ChangeLog is
no longer included ?
Or do we need a transition period deprecating the old way and
including the
On Thu, 08 Oct 2009 16:10:05 +0200
Cedric Staniewski wrote:
> Hi,
>
> This patch adds a new PKGBUILD variable, changelog, which replaces
> the old, hardcoded ChangeLog file. The old behavior is completely
> removed, which means that existing ChangeLog files will be ignored if
> there is no appro
On Sat 10 Oct 2009 16:40 +0200, Xavier wrote:
> On Sat, Oct 10, 2009 at 4:37 PM, Xavier wrote:
> >
> > This looked good to me.
> >
>
> Sorry for the double mail.
>
> I just had one question :
> Will every package maintainer figure out easily that his ChangeLog is
> no longer included ?
> Or do w
Cedric Staniewski wrote:
Hi,
This patch adds a new PKGBUILD variable, changelog, which replaces the old,
hardcoded ChangeLog file. The old behavior is completely removed, which means
that existing ChangeLog files will be ignored if there is no appropriate line
in the PKGBUILD. For a more deta
On Thu, Oct 8, 2009 at 9:10 AM, Cedric Staniewski wrote:
> Currently, a changelog is added to a package if a specific file with a
> hardcoded name exists in the PKGBUILD's directory. This approach is not
> pretty and also inconsistent with the handling of install files, but it
> works.
>
> With th
Dan McGee wrote:
On Thu, Oct 8, 2009 at 9:10 AM, Cedric Staniewski wrote:
Currently, a changelog is added to a package if a specific file with a
hardcoded name exists in the PKGBUILD's directory. This approach is not
pretty and also inconsistent with the handling of install files, but it
wor
On Sun, Oct 11, 2009 at 5:12 PM, Allan McRae wrote:
> Dan McGee wrote:
>>
>> On Thu, Oct 8, 2009 at 9:10 AM, Cedric Staniewski wrote:
>>
>>>
>>> Currently, a changelog is added to a package if a specific file with a
>>> hardcoded name exists in the PKGBUILD's directory. This approach is not
>>> p
Loui Chang wrote:
> On Sat 10 Oct 2009 16:40 +0200, Xavier wrote:
>> On Sat, Oct 10, 2009 at 4:37 PM, Xavier wrote:
>>> This looked good to me.
>>>
>> Sorry for the double mail.
>>
>> I just had one question :
>> Will every package maintainer figure out easily that his ChangeLog is
>> no longer in
Dan McGee wrote:
> On Sun, Oct 11, 2009 at 5:12 PM, Allan McRae wrote:
>> Dan McGee wrote:
>>> On Thu, Oct 8, 2009 at 9:10 AM, Cedric Staniewski wrote:
>>>
Currently, a changelog is added to a package if a specific file with a
hardcoded name exists in the PKGBUILD's directory. This appr
12 matches
Mail list logo
