> I don't even know what you are talking about, there is no "replacement"
> system and I never suggested there was.

Okay, sure, so I added the term "replacement" to what you said because that's 
how I understood it when I read it (as in "drop-in replacement"). My mistake.


> What I said was that libmakepkg
> is by definition extendable by simply dropping in new components, which
> shouldn't be news to anyone...

Well, TBH, it's news to me. I've never seen any documentation about what you 
are describing nor have I ever seen it mentioned anywhere online that I 
frequent. Do you have any links I can reference to know what you are talking 
about. I'm trying to understand how I should go about implementing what I 
proposed in the way that you suggested implementing such a feature should be 
done if it's done at all. 


> Also, your emails look a bit wonky -- your top-posted responses to
> selected quotes appear above what seems to be a *forwarded* message,
> which is honestly kind of confusing to read.

Sorry, there's not much I can do about it. I don't have any option to reply in 
the style that you are using with my client.


  -- 
 Dustin Falgout 
 
     




From: pacman-dev <[email protected]> on behalf of Eli Schwartz 
<[email protected]>
Sent: Saturday, April 22, 2017 10:03 PM
To: [email protected]
Subject: Re: [pacman-dev] [RFC] Make PKGBUILD attributes configurable
    
On 04/22/2017 10:18 PM, Dustin Falgout wrote:
> That sounds sensible to me. I didn't realize there was already a
> drop-in replacement system for makepkg. How does it work?

I don't even know what you are talking about, there is no "replacement"
system and I never suggested there was. What I said was that libmakepkg
is by definition extendable by simply dropping in new components, which
shouldn't be news to anyone...

The source contains many examples of how to extend a bash array. :)

...

Also, your emails look a bit wonky -- your top-posted responses to
selected quotes appear above what seems to be a *forwarded* message,
which is honestly kind of confusing to read.

Also, your paragraphs don't line-wrap properly, which should only happen
in HTML emails since HTML emails have better ways of doing text layout.

-- 
Eli Schwartz

    

Reply via email to