public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
* [gentoo-dev] integrating solaris overlay into main portage
@ 2007-10-10 15:31 Christian Parpart
  2007-10-10 15:49 ` Fabian Groffen
  2007-10-11 14:51 ` Mike Frysinger
  0 siblings, 2 replies; 3+ messages in thread
From: Christian Parpart @ 2007-10-10 15:31 UTC (permalink / raw
  To: gentoo-dev@lists.gentoo.org

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

Hi all,

i always feared in asking this because of some typical flamewars, however.

I am now in a company which is actively using Solaris 10 and Gentoo. We're 
deploying some house-written software onto both using the portage system (!).

However, knowing that portage for Solaris (10) is only available via a prefix 
is not the problem, but knowing that for solaris you have to use a completely 
different portage tree which is just lagging behind is a real pain.

i'm not that familiar with this prefixed development as the maintainers 
itself, but i don't think it's a big deal to tag those ebuilds with 
solaris-x86 (for example) that are $EPREFIX aware, isn't it?

The benifit: we have so many ebuilds in the tree that just need keywording 
and/or a simple $EPREFIX addition. This shouldn't hurt any primary package 
maintainer in finding any of these in their ebuilds, in fact, i'd be happy to 
know there's yet another package that can be installed using gentoo's portage 
on yet another architecture.

How do you feel with that idea?

Regards,
Christian Parpart.

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [gentoo-dev] integrating solaris overlay into main portage
  2007-10-10 15:31 [gentoo-dev] integrating solaris overlay into main portage Christian Parpart
@ 2007-10-10 15:49 ` Fabian Groffen
  2007-10-11 14:51 ` Mike Frysinger
  1 sibling, 0 replies; 3+ messages in thread
From: Fabian Groffen @ 2007-10-10 15:49 UTC (permalink / raw
  To: gentoo-dev

Hi Christian,

On 10-10-2007 17:31:17 +0200, Christian Parpart wrote:
...
> However, knowing that portage for Solaris (10) is only available via a prefix 
> is not the problem, but knowing that for solaris you have to use a completely 
> different portage tree which is just lagging behind is a real pain.

Which/what tree are you using?

> i'm not that familiar with this prefixed development as the maintainers 
> itself, but i don't think it's a big deal to tag those ebuilds with 
> solaris-x86 (for example) that are $EPREFIX aware, isn't it?

Which system are you using?

I know of three such systems, that's why I'm asking.


-- 
Fabian Groffen
Gentoo on a different level
-- 
gentoo-dev@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [gentoo-dev] integrating solaris overlay into main portage
  2007-10-10 15:31 [gentoo-dev] integrating solaris overlay into main portage Christian Parpart
  2007-10-10 15:49 ` Fabian Groffen
@ 2007-10-11 14:51 ` Mike Frysinger
  1 sibling, 0 replies; 3+ messages in thread
From: Mike Frysinger @ 2007-10-11 14:51 UTC (permalink / raw
  To: gentoo-dev

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

On Wednesday 10 October 2007, Christian Parpart wrote:
> How do you feel with that idea?

if all you're doing is adding a new KEYWORD to an ebuild, you can just do 
it ... you dont need permission to go around running `ekeyword`
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 827 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2007-10-11 15:06 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-10-10 15:31 [gentoo-dev] integrating solaris overlay into main portage Christian Parpart
2007-10-10 15:49 ` Fabian Groffen
2007-10-11 14:51 ` Mike Frysinger

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox