Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
Bigtop >> mail # user >> How do the spec files get / reference source?


Copy link to this message
-
Re: How do the spec files get / reference source?
On Sat, Oct 5, 2013 at 12:45 PM, Jay Vyas <[EMAIL PROTECTED]> wrote:
> Where does the source come from in the various bigtop-packages?

Depends of what you mean by 'source'.

> I see references to things like
>
> "flume_folder" (in flume.spec) and
> things like "Source0:
> %{name}-distribution-%{mahout_base_version}-src.tar.gz" (mahout.spec)
>
> etc.... but am not sure where the actual source code is pulled in  inside of
> these .spec files.
>
> This might also be a general .spec question, if so apologies in advance.

Most of the source comes from 2 places:
    * bigtop-package/src/common/<component>
    * bigtop-package/src/rpm/SOURCES

With an exception of the source tarball which gets downloaded
from the target location (recorded in bigtop.mk).

All of this is coded in package.mk -- that's your source of truth.

Thanks,
Roman.
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB