[aur-general] question about git package as a dependency
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 for the user is that helpers like yaourt won't find the dependency. I was wondering what you guys think about this... Greetings, lieven
On 27 November 2013 04:43, Lieven Moors <lievenmoors@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 functionality of ntk is not required by non-daw-git. So just nudge the ntk-git maintainer. -- GPG/PGP ID: C0711BF1
On Wed, Nov 27, 2013 at 05:20:43AM +0800, Rashif Ray Rahman wrote:
On 27 November 2013 04:43, Lieven Moors <lievenmoors@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 functionality of ntk is not required by non-daw-git. So just nudge the ntk-git maintainer.
With devel functionality, do you mean header files? Wouldn't they be needed to build non-daw-git anyway? The problem is that ntk-git has been in a state of constant flux, and non-daw-git would often refuse to build, unless you rebuild ntk-git first...
On 28 November 2013 02:27, Lieven Moors <lievenmoors@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 constant flux, and non-daw-git would often refuse to build, unless you rebuild ntk-git first...
Then you should just depend on ntk (but doesn't make a difference if a git development source is all there is). -- GPG/PGP ID: C0711BF1
On Thu, Nov 28, 2013 at 02:41:42AM +0800, Rashif Ray Rahman wrote:
On 28 November 2013 02:27, Lieven Moors <lievenmoors@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 constant flux, and non-daw-git would often refuse to build, unless you rebuild ntk-git first...
Then you should just depend on ntk (but doesn't make a difference if a git development source is all there is).
Yes, I think I'll keep depending on ntk. There might be a stable ntk in the near future, and then I'll see how non-daw-git behaves with that. Thanks for your help, lieven
On Tue, Nov 26, 2013 at 6:43 PM, Lieven Moors <lievenmoors@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 provide ntk, and non-daw-git should depend on some git-release of ntk. The downside for the user is that helpers like yaourt won't find the dependency.
BTW, I just did a small test here and yaourt does find the ntk-git dependency through AUR.
I was wondering what you guys think about this...
Greetings,
lieven
--- Gabriel B. Casella "Nothing is impossible, impossible just takes longer"
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 <lievenmoors@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 provide ntk, and non-daw-git should depend on some git-release of ntk. The downside for the user is that helpers like yaourt won't find the dependency.
BTW, I just did a small test here and yaourt does find the ntk-git dependency through AUR.
Ah, I should have checked it myself again. I think the problem was that AUR doesn't allow you to search for provides through the web interface. And another problem was that when you rebuild non-daw-git, you forget that most of the time you have to rebuild ntk-git as well, and yaourt has no way of knowing that. I already left a message for the ntk-git maintainer. If he would include the commit count in the version string, it should be possible to depend on a specific git "release". I guess that would be the best solution... lieven
participants (3)
-
Gabriel B. Casella
-
Lieven Moors
-
Rashif Ray Rahman