From: Felipe Contreras <felipe.contreras@gmail.com>
To: Suvayu Ali <fatkasuvayu+linux@gmail.com>,
Felipe Contreras <felipe.contreras@gmail.com>
Cc: notmuch@notmuchmail.org
Subject: Re: Submodules for language bindings (was: Github?)
Date: Fri, 09 May 2014 08:09:37 -0500 [thread overview]
Message-ID: <536cd39189c55_4ea9112f308ab@nysa.notmuch> (raw)
In-Reply-To: <20140509125004.GF2634@chitra.no-ip.org>
Suvayu Ali wrote:
> On Fri, May 09, 2014 at 07:40:27AM -0500, Felipe Contreras wrote:
> > Suvayu Ali wrote:
> >
> > > To explain my point with RPM specifics, if I were to
> > > use separate spec files, python-notmuch would have:
> > >
> > > Requires: notmuch >= <version-string>
> > >
> > > As you can see this only allows for tracking dependency based on
> > > official version numbers. With more bindings, many with different
> > > version dependencies, this becomes quite cumbersome;
> >
> > No, it doesn't:
> >
> > %package notmuch-ruby
> > Requires: notmuch = %{version}-%{release}, ruby
>
> Doesn't that work when you have one spec file for all sub-packages (as I
> do now)? I was responding to Trevor's suggestion about not having
> sub-packages, IOW, different spec files for different packages.
Ah. I don't see why anybody would want different spec files for
different subpackages.
--
Felipe Contreras
next prev parent reply other threads:[~2014-05-09 13:09 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-08 5:28 Github? Wael Nasreddine
2014-05-08 5:30 ` Github? Wael Nasreddine
2014-05-08 7:23 ` Github? Jani Nikula
2014-05-08 7:13 ` Github? Jani Nikula
2014-05-08 8:40 ` Github? Eric
2014-05-08 10:13 ` Github? Guyzmo
2014-05-08 19:54 ` Github? Wael Nasreddine
2014-05-08 20:14 ` Github? Wael M. Nasreddine
2014-05-08 20:23 ` Github? Felipe Contreras
2014-05-08 20:30 ` Github? Suvayu Ali
2014-05-08 21:21 ` Github? guyzmo
2014-05-08 22:00 ` Github? Suvayu Ali
2014-05-08 22:29 ` Submodules for language bindings (was: Github?) W. Trevor King
2014-05-08 22:45 ` Suvayu Ali
2014-05-08 23:35 ` W. Trevor King
2014-05-09 11:39 ` Suvayu Ali
2014-05-09 12:40 ` Felipe Contreras
2014-05-09 12:50 ` Suvayu Ali
2014-05-09 13:09 ` Felipe Contreras [this message]
2014-05-09 2:45 ` Github? Felipe Contreras
2014-05-08 20:23 ` Github? W. Trevor King
2014-05-08 22:39 ` Github? David Bremner
2014-05-08 23:18 ` Github? Wael Nasreddine
2014-05-08 23:49 ` Github? W. Trevor King
2014-05-09 0:13 ` Github? Wael Nasreddine
2014-05-09 2:28 ` Github? W. Trevor King
2014-05-09 2:44 ` Github? Felipe Contreras
2014-05-09 2:43 ` Github? Felipe Contreras
2014-05-09 2:56 ` Github? Wael Nasreddine
2014-05-09 2:54 ` Github? Felipe Contreras
2014-05-09 3:01 ` Github? W. Trevor King
2014-05-09 3:08 ` Github? Felipe Contreras
2014-05-09 3:08 ` Github? Douglas Campos
2014-05-09 2:31 ` Github? Felipe Contreras
2014-05-08 23:30 ` Github? David Bremner
2014-05-09 12:13 ` Github? Amadeusz Żołnowski
2014-05-09 12:37 ` Github? Felipe Contreras
2014-05-10 1:21 ` Github? David Bremner
2014-05-10 5:08 ` Github? Wael M. Nasreddine
2014-05-10 7:49 ` Github? Tomi Ollila
2014-05-10 8:22 ` Github? Felipe Contreras
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=536cd39189c55_4ea9112f308ab@nysa.notmuch \
--to=felipe.contreras@gmail.com \
--cc=fatkasuvayu+linux@gmail.com \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).