On Wed, Nov 27, 2013 at 05:20:43AM +0800, Rashif Ray Rahman wrote:
On 27 November 2013 04:43, Lieven Moors lievenmo...@gmail.com wrote:
I think technically, ntk-git should provide
ntk, and non-daw-git should depend on some git-release
of ntk.
You can depend on ntk-git, but a better
On Tue, Nov 26, 2013 at 07:28:17PM -0200, Gabriel B. Casella wrote:
On Tue, Nov 26, 2013 at 6:43 PM, Lieven Moors lievenmo...@gmail.com wrote:
Hi,
I was wondering if it would be ok to let my package
(non-daw-git) depend on the ntk-git package instead of
ntk. The package ntk is not yet
On 28 November 2013 02:27, Lieven Moors lievenmo...@gmail.com wrote:
With devel functionality, do you mean header files? Wouldn't they
be needed to build non-daw-git anyway?
I meant experimental functionality (i.e. development branch).
The problem is that ntk-git has been in a state of
On Thu, Nov 28, 2013 at 02:41:42AM +0800, Rashif Ray Rahman wrote:
On 28 November 2013 02:27, Lieven Moors lievenmo...@gmail.com wrote:
With devel functionality, do you mean header files? Wouldn't they
be needed to build non-daw-git anyway?
I meant experimental functionality (i.e.
Hi,
I was wondering if it would be ok to let my package
(non-daw-git) depend on the ntk-git package instead of
ntk. The package ntk is not yet available in AUR, but
ntk-git is. I think technically, ntk-git should provide
ntk, and non-daw-git should depend on some git-release
of ntk. The downside
On 27 November 2013 04:43, Lieven Moors lievenmo...@gmail.com wrote:
I think technically, ntk-git should provide
ntk, and non-daw-git should depend on some git-release
of ntk.
You can depend on ntk-git, but a better approach is to have ntk-git
provide ntk, and depend on that -- if devel
On Tue, Nov 26, 2013 at 6:43 PM, Lieven Moors lievenmo...@gmail.com wrote:
Hi,
I was wondering if it would be ok to let my package
(non-daw-git) depend on the ntk-git package instead of
ntk. The package ntk is not yet available in AUR, but
ntk-git is. I think technically, ntk-git should
