You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by Ruijing Guo <rg...@pivotal.io> on 2014/11/06 06:47:44 UTC
Questions about parameters in bigtop.mk
Some Questions about parameters in bigtop.mk:
Example:
HBASE_NAME=hbase
HBASE_RELNOTES_NAME=Apache HBase
HBASE_PKG_NAME=hbase
HBASE_BASE_VERSION=0.98.5
HBASE_PKG_VERSION=$(HBASE_BASE_VERSION)
HBASE_RELEASE_VERSION=1
HBASE_TARBALL_DST=hbase-$(HBASE_BASE_VERSION).tar.gz
HBASE_TARBALL_SRC=hbase-$(HBASE_BASE_VERSION)-src.tar.gz
HBASE_DOWNLOAD_PATH=/hbase/hbase-$(HBASE_BASE_VERSION)
HBASE_SITE=$(APACHE_MIRROR)$(HBASE_DOWNLOAD_PATH)
HBASE_ARCHIVE=$(APACHE_ARCHIVE)$(HBASE_DOWNLOAD_PATH)
In this example:
1. what's difference between HBASE_NAME & HBASE_PKG_NAME?
2. what's difference between HBASE_BASE_VERSION & HBASE_PKG_VERSION?
BASE_VERSION is jar verion? PKG_VERSION is rpm version?
3. why we need HBASE_TARBALL_DST & HBASE_TARBALL_SRC?
I think that we don't need *_DST, *_SRC, *_SITE, *_ARCHIVE and
HBASE_DOWNLOAD_PATH = <xxx> is enough
--
Thanks,
-Ruijing
Re: Questions about parameters in bigtop.mk
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
I see no reason to introduce a vendor specific sub-strings.
You can always override the entire string with whatever
you desire during the build process itself.
Thanks,
Roman.
On Wed, Nov 5, 2014 at 11:02 PM, Ruijing Guo <rg...@pivotal.io> wrote:
> The motivation is to add some vendor specific in bigtop.mk. the example is
> like:
>
> #VENDOR_VERSION = .bigtop.0.9 <<< we can disable here
>
> VENDOR_RELEASE = 100
>
> HBASE_BASE_NAME=hbase
> HBASE_RELNOTES_NAME=Apache HBase
> HBASE_APACHE_VERSION = 0.98.5 (new vars)
> HBASE_BASE_VERSION=$(HBASE_APACHE_VERSION)$(VENDOR_VERSION)-$(VENDOR_RELEASE)
> HBASE_PKG_NAME=hbase
> HBASE_PKG_VERSION=$(HBASE_APACHE_VERSION)$(VENDOR_VERSION)
> HBASE_RELEASE_VERSION=$(VENDOR_RELEASE)
> HBASE_SRC_DOWNLOAD=<xxxx>
>
> so that we can generate package & RPM as:
>
> RPM: hbase-0.98.5.bigtop.0.9-100.el6.noarch.rpm
>
> JAR: hadoop-auth-2.4.1.bigtop.0.9-100.jar
>
>
>
> On Thu, Nov 6, 2014 at 2:30 PM, Konstantin Boudnik <co...@apache.org> wrote:
>
>> Package name could be different from the base name. The good example is
>> datafu
>> component. Same goes with versions. PKG_VERSION might include vendor
>> specific
>> tags or maintainer tags.
>>
>> TARBALL_SRC is where the download tarball is stored. The _DST one is for
>> the
>> creation of the package: the source for the source- and binary-packages.
>>
>> _SITE and _ARCHIVE are main and alternative (backup) download locations for
>> the component tarball.
>>
>> You can run something like
>> gradle component-info
>>
>> to investigate this and more for yourself.
>>
>> We might reduce some of these vars, but let's figure out first what is the
>> objective. Would you mind sharing your story?
>>
>> Cos
>>
>> On Thu, Nov 06, 2014 at 01:47PM, Ruijing Guo wrote:
>> > Some Questions about parameters in bigtop.mk:
>> >
>> > Example:
>> >
>> > HBASE_NAME=hbase
>> > HBASE_RELNOTES_NAME=Apache HBase
>> > HBASE_PKG_NAME=hbase
>> > HBASE_BASE_VERSION=0.98.5
>> > HBASE_PKG_VERSION=$(HBASE_BASE_VERSION)
>> > HBASE_RELEASE_VERSION=1
>> > HBASE_TARBALL_DST=hbase-$(HBASE_BASE_VERSION).tar.gz
>> > HBASE_TARBALL_SRC=hbase-$(HBASE_BASE_VERSION)-src.tar.gz
>> > HBASE_DOWNLOAD_PATH=/hbase/hbase-$(HBASE_BASE_VERSION)
>> > HBASE_SITE=$(APACHE_MIRROR)$(HBASE_DOWNLOAD_PATH)
>> > HBASE_ARCHIVE=$(APACHE_ARCHIVE)$(HBASE_DOWNLOAD_PATH)
>> >
>> >
>> > In this example:
>> >
>> > 1. what's difference between HBASE_NAME & HBASE_PKG_NAME?
>> >
>> > 2. what's difference between HBASE_BASE_VERSION & HBASE_PKG_VERSION?
>> >
>> > BASE_VERSION is jar verion? PKG_VERSION is rpm version?
>> >
>> > 3. why we need HBASE_TARBALL_DST & HBASE_TARBALL_SRC?
>> >
>> > I think that we don't need *_DST, *_SRC, *_SITE, *_ARCHIVE and
>> > HBASE_DOWNLOAD_PATH = <xxx> is enough
>> >
>> > --
>> > Thanks,
>> > -Ruijing
>>
>
>
>
> --
> Thanks,
> -Ruijing
Re: Questions about parameters in bigtop.mk
Posted by Ruijing Guo <rg...@pivotal.io>.
The motivation is to add some vendor specific in bigtop.mk. the example is
like:
#VENDOR_VERSION = .bigtop.0.9 <<< we can disable here
VENDOR_RELEASE = 100
HBASE_BASE_NAME=hbase
HBASE_RELNOTES_NAME=Apache HBase
HBASE_APACHE_VERSION = 0.98.5 (new vars)
HBASE_BASE_VERSION=$(HBASE_APACHE_VERSION)$(VENDOR_VERSION)-$(VENDOR_RELEASE)
HBASE_PKG_NAME=hbase
HBASE_PKG_VERSION=$(HBASE_APACHE_VERSION)$(VENDOR_VERSION)
HBASE_RELEASE_VERSION=$(VENDOR_RELEASE)
HBASE_SRC_DOWNLOAD=<xxxx>
so that we can generate package & RPM as:
RPM: hbase-0.98.5.bigtop.0.9-100.el6.noarch.rpm
JAR: hadoop-auth-2.4.1.bigtop.0.9-100.jar
On Thu, Nov 6, 2014 at 2:30 PM, Konstantin Boudnik <co...@apache.org> wrote:
> Package name could be different from the base name. The good example is
> datafu
> component. Same goes with versions. PKG_VERSION might include vendor
> specific
> tags or maintainer tags.
>
> TARBALL_SRC is where the download tarball is stored. The _DST one is for
> the
> creation of the package: the source for the source- and binary-packages.
>
> _SITE and _ARCHIVE are main and alternative (backup) download locations for
> the component tarball.
>
> You can run something like
> gradle component-info
>
> to investigate this and more for yourself.
>
> We might reduce some of these vars, but let's figure out first what is the
> objective. Would you mind sharing your story?
>
> Cos
>
> On Thu, Nov 06, 2014 at 01:47PM, Ruijing Guo wrote:
> > Some Questions about parameters in bigtop.mk:
> >
> > Example:
> >
> > HBASE_NAME=hbase
> > HBASE_RELNOTES_NAME=Apache HBase
> > HBASE_PKG_NAME=hbase
> > HBASE_BASE_VERSION=0.98.5
> > HBASE_PKG_VERSION=$(HBASE_BASE_VERSION)
> > HBASE_RELEASE_VERSION=1
> > HBASE_TARBALL_DST=hbase-$(HBASE_BASE_VERSION).tar.gz
> > HBASE_TARBALL_SRC=hbase-$(HBASE_BASE_VERSION)-src.tar.gz
> > HBASE_DOWNLOAD_PATH=/hbase/hbase-$(HBASE_BASE_VERSION)
> > HBASE_SITE=$(APACHE_MIRROR)$(HBASE_DOWNLOAD_PATH)
> > HBASE_ARCHIVE=$(APACHE_ARCHIVE)$(HBASE_DOWNLOAD_PATH)
> >
> >
> > In this example:
> >
> > 1. what's difference between HBASE_NAME & HBASE_PKG_NAME?
> >
> > 2. what's difference between HBASE_BASE_VERSION & HBASE_PKG_VERSION?
> >
> > BASE_VERSION is jar verion? PKG_VERSION is rpm version?
> >
> > 3. why we need HBASE_TARBALL_DST & HBASE_TARBALL_SRC?
> >
> > I think that we don't need *_DST, *_SRC, *_SITE, *_ARCHIVE and
> > HBASE_DOWNLOAD_PATH = <xxx> is enough
> >
> > --
> > Thanks,
> > -Ruijing
>
--
Thanks,
-Ruijing
Re: Questions about parameters in bigtop.mk
Posted by Konstantin Boudnik <co...@apache.org>.
Package name could be different from the base name. The good example is datafu
component. Same goes with versions. PKG_VERSION might include vendor specific
tags or maintainer tags.
TARBALL_SRC is where the download tarball is stored. The _DST one is for the
creation of the package: the source for the source- and binary-packages.
_SITE and _ARCHIVE are main and alternative (backup) download locations for
the component tarball.
You can run something like
gradle component-info
to investigate this and more for yourself.
We might reduce some of these vars, but let's figure out first what is the
objective. Would you mind sharing your story?
Cos
On Thu, Nov 06, 2014 at 01:47PM, Ruijing Guo wrote:
> Some Questions about parameters in bigtop.mk:
>
> Example:
>
> HBASE_NAME=hbase
> HBASE_RELNOTES_NAME=Apache HBase
> HBASE_PKG_NAME=hbase
> HBASE_BASE_VERSION=0.98.5
> HBASE_PKG_VERSION=$(HBASE_BASE_VERSION)
> HBASE_RELEASE_VERSION=1
> HBASE_TARBALL_DST=hbase-$(HBASE_BASE_VERSION).tar.gz
> HBASE_TARBALL_SRC=hbase-$(HBASE_BASE_VERSION)-src.tar.gz
> HBASE_DOWNLOAD_PATH=/hbase/hbase-$(HBASE_BASE_VERSION)
> HBASE_SITE=$(APACHE_MIRROR)$(HBASE_DOWNLOAD_PATH)
> HBASE_ARCHIVE=$(APACHE_ARCHIVE)$(HBASE_DOWNLOAD_PATH)
>
>
> In this example:
>
> 1. what's difference between HBASE_NAME & HBASE_PKG_NAME?
>
> 2. what's difference between HBASE_BASE_VERSION & HBASE_PKG_VERSION?
>
> BASE_VERSION is jar verion? PKG_VERSION is rpm version?
>
> 3. why we need HBASE_TARBALL_DST & HBASE_TARBALL_SRC?
>
> I think that we don't need *_DST, *_SRC, *_SITE, *_ARCHIVE and
> HBASE_DOWNLOAD_PATH = <xxx> is enough
>
> --
> Thanks,
> -Ruijing