[gentoo-dev] Selection for KDE base-packages

[gentoo-dev] Selection for KDE base-packages

[Sebastian Werner]

Hello,

i don't like to install all these applications which come with kde-2.2. 

So i installed them manually all the time before.

Could we change the ebuilds to patch the toplevel makefile in each package to 
disable the entire dir of 'kedit' for example. I have no idea how we 
configure this option with USE-flags or so. 

Thanks,

Sebastian

Re: [gentoo-dev] Selection for KDE base-packages

[Dan Armak]

You mean, you want kdebase, but only it's core parts i.e. kicker? Well, I 
could make a (separate) ebuild for that sometime. Is that what you want?


-- 

Dan Armak
Gentoo Linux Developer, Desktop Team
Matan, Israel

Re: [gentoo-dev] Selection for KDE base-packages

[Mikael Hallendal]

Den 24 Aug 2001 01:32:21 +0300 skrev Dan Armak:
> You mean, you want kdebase, but only it's core parts i.e. kicker? Well, I 
> could make a (separate) ebuild for that sometime. Is that what you want?

Do you mean to extract parts from one single tarball? Is that a good
idea? 

Regards,
  Mikael Hallendal

-- 

Mikael Hallendal
Gentoo Linux Developer, Desktop Team Leader
Stockholm, Sweden

Re: [gentoo-dev] Selection for KDE base-packages

[Dan Armak]

> Do you mean to extract parts from one single tarball? Is that a good
> idea?
No, in KDE, you can extract the entire tarball, configure the entire tarball, 
and then make/make install in subdirectory separately. Usually you do so in 
the root directory and let it be recursive, but you can also do it in select 
child dirs and skip some.




-- 

Dan Armak
Gentoo Linux Developer, Desktop Team
Matan, Israel

AW: [gentoo-dev] Selection for KDE base-packages

[Sebastian Werner]

The root makefile contains a variable TOPSUBDIRS which select the
subdirs to build and install.
We could patch this file to delete some entries in this variable.

I mean that i don't want to use three editors for example. I need
only one editor in KDE: kate
So i wouldn't install kedit for example

I don't know how to patch this. I preferred sed but it's not so easy :-(

Something like this:

cat Makefile | grep TOPSUBDIRS | sed s/"kedit"/""/g > Makefile

If somebody could do this, thanks... ;-)

Sebastian

-----Ursprüngliche Nachricht-----
Von: gentoo-dev-admin@cvs.gentoo.org
[mailto:gentoo-dev-admin@cvs.gentoo.org]Im Auftrag von Dan Armak
Gesendet: Freitag, 24. August 2001 09:45
An: gentoo-dev@cvs.gentoo.org
Betreff: Re: [gentoo-dev] Selection for KDE base-packages



> Do you mean to extract parts from one single tarball? Is that a good
> idea?
No, in KDE, you can extract the entire tarball, configure the entire
tarball,
and then make/make install in subdirectory separately. Usually you do so in
the root directory and let it be recursive, but you can also do it in select
child dirs and skip some.




--

Dan Armak
Gentoo Linux Developer, Desktop Team
Matan, Israel


_______________________________________________
gentoo-dev mailing list
gentoo-dev@cvs.gentoo.org
http://cvs.gentoo.org/mailman/listinfo/gentoo-dev

Re: AW: [gentoo-dev] Selection for KDE base-packages

[Dan Armak]

I don't think there's many enough people who'd want that to justify writing a 
separate ebuild. If you want a custom configuration, do:

# cd /usr/portage/kde-base/kdebase
# ebuild kdebase-2.2.ebuild unpack
# cd /tmp/portage/kdebase-2.2/work/kdebase-2.2
(edit 'subdirs' here, delete/comment out those you don't want)
# cd /usr/portage/kde-base/kdebase
# ebuild kdebase-2.2.ebuild install
# ebuild kdebase-2.2.ebuild qmerge

That should do it.



-- 

Dan Armak
Gentoo Linux Developer, Desktop Team
Matan, Israel

Re: AW: [gentoo-dev] Selection for KDE base-packages

[Mikael Hallendal]

Den 24 Aug 2001 11:04:59 +0200 skrev Sebastian Werner:
> The root makefile contains a variable TOPSUBDIRS which select the
> subdirs to build and install.
> We could patch this file to delete some entries in this variable.
> 
> I mean that i don't want to use three editors for example. I need
> only one editor in KDE: kate
> So i wouldn't install kedit for example

What about the people that _do_ want kedit and not kate?
I would like some pre-build configuration stuff. With a question to the
user, do you want to configure this package before building it? It would
make the Portage tree more flexible than just using USE-variables. I'm
not sure if this fits into the Portage system though.

But in this case it would be something like:

Do you want to configure KDE-base [y/N]: Y
Which editor would you like: [Kate/kedit/all]: <enter>
...
Installing KDE-base with the following programs:
Editor: Kate
...
Is this correct [Y/n]: <enter>
Start installing..

We could have some kind of timeout on the first question so that if you
do an automatic build it wouldn't stop at the question if you are not at
the computer.

What do you think, drobbins?

Regards,
  Mikael Hallendal

-- 

Mikael Hallendal
Gentoo Linux Developer, Desktop Team Leader
Stockholm, Sweden

Re: AW: [gentoo-dev] Selection for KDE base-packages

[Achim Gottinger]

Sebastian Werner wrote:
> 
> The root makefile contains a variable TOPSUBDIRS which select the
> subdirs to build and install.
> We could patch this file to delete some entries in this variable.
> 
> I mean that i don't want to use three editors for example. I need
> only one editor in KDE: kate
> So i wouldn't install kedit for example
> 
> I don't know how to patch this. I preferred sed but it's not so easy :-(
> 
> Something like this:
> 
> cat Makefile | grep TOPSUBDIRS | sed s/"kedit"/""/g > Makefile
> 
> If somebody could do this, thanks... ;-)
> 
an easier way is to simply remove the subdirs of the unwanted packages
and run

make -f admin/Makefile.common

before configure

bye achim~

Re: AW: [gentoo-dev] Selection for KDE base-packages

[Jerry A!]

On Fri, Aug 24, 2001 at 01:04:35PM +0200, Mikael Hallendal wrote:
: Den 24 Aug 2001 11:04:59 +0200 skrev Sebastian Werner:
: > The root makefile contains a variable TOPSUBDIRS which select the
: > subdirs to build and install.
: > We could patch this file to delete some entries in this variable.
: >
: > I mean that i don't want to use three editors for example. I need
: > only one editor in KDE: kate
: > So i wouldn't install kedit for example
:
: What about the people that _do_ want kedit and not kate?
: I would like some pre-build configuration stuff. With a question to the
: user, do you want to configure this package before building it? It would
: make the Portage tree more flexible than just using USE-variables. I'm
: not sure if this fits into the Portage system though.
:
: But in this case it would be something like:
:
: Do you want to configure KDE-base [y/N]: Y
: Which editor would you like: [Kate/kedit/all]: <enter>
: ...
: Installing KDE-base with the following programs:
: Editor: Kate
: ...
: Is this correct [Y/n]: <enter>
: Start installing..
:
: We could have some kind of timeout on the first question so that if you
: do an automatic build it wouldn't stop at the question if you are not at
: the computer.
:
: What do you think, drobbins?

I think that this goes against the current vision of the portage system.
Currently, a portage should build w/out *any* user interaction.  There
are still some bugs to get worked out, but I think that's still where
we're heading.  Keep in mind, I'm not speaking for Dan, just relating
things as I understand them.

That being said, I want to once again point out that the portage system
does allow one to have a /usr/portage/local directory.  Have you thought
about configuring the ebuild to meet your specific needs and sticking it
in there?

        --Jerry

name:  Jerry Alexandratos         ||  Open-Source software isn't a
phone: 703.599.6023               ||  matter of life or death...
email: jerry@thehutt.org          ||  ...It's much more important
                                  ||  than that!

Re: AW: [gentoo-dev] Selection for KDE base-packages

[Mikael Hallendal]

Den 24 Aug 2001 10:55:34 -0400 skrev Jerry A!:

> I think that this goes against the current vision of the portage system.
> Currently, a portage should build w/out *any* user interaction.  There
> are still some bugs to get worked out, but I think that's still where
> we're heading.  Keep in mind, I'm not speaking for Dan, just relating
> things as I understand them.

That is why I proposed the time-out feature. It will build (with
default-settings) without any user interaction, howevery you are given
the possibility to configure the build.

> That being said, I want to once again point out that the portage system
> does allow one to have a /usr/portage/local directory.  Have you thought
> about configuring the ebuild to meet your specific needs and sticking it
> in there?

Does this work now? This was one of the first things I asked for when
starting on Gentoo, it's still in the todo though so I'd say that it
isn't possible yet. Or am I wrong (no one would be happier).

Regards, 
  Mikael Hallendal

-- 

Mikael Hallendal
Gentoo Linux Developer, Desktop Team Leader
CodeFactory AB, Stockholm, Sweden

Re: AW: [gentoo-dev] Selection for KDE base-packages

[Daniel Robbins]

On Fri, Aug 24, 2001 at 01:04:35PM +0200, Mikael Hallendal wrote:
> What about the people that _do_ want kedit and not kate?
> I would like some pre-build configuration stuff. With a question to the
> user, do you want to configure this package before building it? It would
> make the Portage tree more flexible than just using USE-variables. I'm
> not sure if this fits into the Portage system though.
> 
> But in this case it would be something like:
> 
> Do you want to configure KDE-base [y/N]: Y
> Which editor would you like: [Kate/kedit/all]: <enter>
> ...
> Installing KDE-base with the following programs:
> Editor: Kate
> ...
> Is this correct [Y/n]: <enter>
> Start installing..
> 
> We could have some kind of timeout on the first question so that if you
> do an automatic build it wouldn't stop at the question if you are not at
> the computer.
> 
> What do you think, drobbins?

I think this could be very nice for Portage 2.0 :)

-- 
Daniel Robbins					<drobbins@gentoo.org>
Chief Architect/President			http://www.gentoo.org 
Gentoo Technologies, Inc.