[gentoo-dev] Add new variable BINARY_KEYWORDS for binary support?

[gentoo-dev] Add new variable BINARY_KEYWORDS for binary support?

[pclouds]

[-- Attachment #1: Type: text/plain, Size: 626 bytes --]

Hi
I noticed there are some binary ebuilds with suffix "-bin" such as
openoffice-bin. I'd propose adding a new variable BINARY_KEYWORDS into
openoffice ebuild and remove openoffice-bin ebuild.
The syntax of BINARY_KEYWORDS is as same as KEYWORDS. When people
prefer binary ebuilds, they can do 
BINARY_KEYWORDS="x86" emerge something
and emerge will do install a tbz2.
When a maintainer decide to add binary support for some arch, they add
new archs to BINARY_KEYWORDS. We may need BINARY_SRC_URI also for tbz2
files. 
We may also form binary arch herds just like arch herds  :)
Is this possible?
-- 
Bi Cờ Lao

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] Add new variable BINARY_KEYWORDS for binary support?

[Marius Mauch]

On 08/14/04  pclouds wrote:

> Hi
> I noticed there are some binary ebuilds with suffix "-bin" such as
> openoffice-bin. I'd propose adding a new variable BINARY_KEYWORDS into
> openoffice ebuild and remove openoffice-bin ebuild.
> The syntax of BINARY_KEYWORDS is as same as KEYWORDS. When people
> prefer binary ebuilds, they can do 
> BINARY_KEYWORDS="x86" emerge something
> and emerge will do install a tbz2.
> When a maintainer decide to add binary support for some arch, they add
> new archs to BINARY_KEYWORDS. We may need BINARY_SRC_URI also for tbz2
> files. 
> We may also form binary arch herds just like arch herds  :)
> Is this possible?

Ehm, why?
This won't work as binary packages usually have a completely different
way of installation (how many binary packages use `./configure; make;
make install` ?), so you'd also need different src_compile and
src_install functions which basically means there is no benefit at all.

Marius

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Add new variable BINARY_KEYWORDS for binary support?

[Mike Frysinger]

On Saturday 14 August 2004 12:23 pm, Marius Mauch wrote:
> This won't work as binary packages usually have a completely different
> way of installation (how many binary packages use `./configure; make;
> make install` ?), so you'd also need different src_compile and
> src_install functions which basically means there is no benefit at all.

agreed
-mike

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Add new variable BINARY_KEYWORDS for binary support?

[pclouds]

[-- Attachment #1: Type: text/plain, Size: 1281 bytes --]

On Sat, Aug 14, 2004 at 06:23:54PM +0200, Marius Mauch wrote:
> On 08/14/04  pclouds wrote:
> 
> > Hi
> > I noticed there are some binary ebuilds with suffix "-bin" such as
> > openoffice-bin. I'd propose adding a new variable BINARY_KEYWORDS into
> > openoffice ebuild and remove openoffice-bin ebuild.
> > The syntax of BINARY_KEYWORDS is as same as KEYWORDS. When people
> > prefer binary ebuilds, they can do 
> > BINARY_KEYWORDS="x86" emerge something
> > and emerge will do install a tbz2.
> > When a maintainer decide to add binary support for some arch, they add
> > new archs to BINARY_KEYWORDS. We may need BINARY_SRC_URI also for tbz2
> > files. 
> > We may also form binary arch herds just like arch herds  :)
> > Is this possible?
> 
> Ehm, why?
> This won't work as binary packages usually have a completely different
> way of installation (how many binary packages use `./configure; make;
> make install` ?), so you'd also need different src_compile and
> src_install functions which basically means there is no benefit at
> all.

It won't use "./configure;make;make install". When you want to
install binary packages, it will fetch the corresponding tbz2 and
install it. src_compile, src_install and others are ignored.

-- 
Bi Cờ Lao

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] Add new variable BINARY_KEYWORDS for binary support?

[Mike Frysinger]

[-- Attachment #1: Type: text/plain, Size: 437 bytes --]

On Sunday 15 August 2004 02:29 am, pclouds wrote:
> It won't use "./configure;make;make install". When you want to
> install binary packages, it will fetch the corresponding tbz2 and
> install it. src_compile, src_install and others are ignored.

what tbz2 ?
we dont produce the -bin packages ourself, they are created upstream ... often 
times they need to be touched up before being merged to the final 
filesystem ...
-mike

[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 838 bytes --]