Albert wrote:
> My pleasure.
> I started with Mandrake 8.0 a long time ago, just for fun, and then for
> my daily use with Mandrake 9.2.
> After some time I looked too often under the hood and broke it. Very
> frustrating experience.
> Gentoo is very good. No plan to move to another one. It is not a distro
> in the sense you don't need to wait for bundled releases.
> The good surprise is that I've never seen any breakdown, just trouble
> when upgrading to the 2.6.8 kernel, with sound and video drivers. Now
> it's allright.
> I think .org distros are going to take a lot of importance.
>
I've been wanting to move to the 2.6.8 kernel. (I DO need
to rebuild a new kernel, I'm still running 2.4.22) but that
means having to go to udev most likely and I've heard of problems
with cd writting. Any advice on how to do this?



> ray wrote:
>
>> On Fri, 22 Oct 2004 00:18:55 +0200, Albert wrote:
>>
>>
>>> http://packages.gentoo.org/
>>>
>>> ray wrote:
>>>
>>>> Is there a list somewhere of what is available to 'emerge'?? I looked
>>>> around the gentoo site but could not find anything. I'd like to see
>>>> that
>>>> first before I go out and get sources for tons of stuff (like
>>>> 'lmsensors').
>>>>
>>>> thanks
>>>>
>>
>>
>> Thanks - that's what I was looking for. Now that's what I call response
>> time!!
>>
>> I'm playing with gentoo on my mini-itx system. So far, quite pleased -
>> I've been running other linux distros for a couple of years.
>>
>>

> One word: Ick. I have yet to see anyone provide a good reason why an
> ebuild should not be used when present. On a typical Gentoo system,
> /usr/local/ should be all but empty. If not, you may be endangering the
> way portage works. Just be careful if you plan to keep doing that ...
>

There are some packages for which there are NO ebuilds, or for which
the ebuilds are VERY out of date. One example is the gnu avr
tools (gdb and compiler ebuilds out of date, NO avarice ebuild
available) SO I will build these in /usr/local.
Why would this break portage? /usr/local should be invisable to
the system. Root usually doesn't even HAVE /usr/local in its path.

On 2004-10-23, Ken Scharf <wa2mzeNOTTHIS@bellsouth.net> wrote:
> Albert wrote:
>> My pleasure.
>> I started with Mandrake 8.0 a long time ago, just for fun, and then for
>> my daily use with Mandrake 9.2.
>> After some time I looked too often under the hood and broke it. Very
>> frustrating experience.
>> Gentoo is very good. No plan to move to another one. It is not a distro
>> in the sense you don't need to wait for bundled releases.
>> The good surprise is that I've never seen any breakdown, just trouble
>> when upgrading to the 2.6.8 kernel, with sound and video drivers. Now
>> it's allright.
>> I think .org distros are going to take a lot of importance.
>>
> I've been wanting to move to the 2.6.8 kernel. (I DO need
> to rebuild a new kernel, I'm still running 2.4.22) but that
> means having to go to udev most likely and I've heard of problems
> with cd writting. Any advice on how to do this?
>
>

You don't *have* to go to udev -- devfs is still an option

Haven't tried udev + cd burning.

--
Jon Portnoy
avenj/irc.freenode.net, irc.oftc.net

Ken Scharf wrote:

>> One word: Ick. I have yet to see anyone provide a good reason why an
>> ebuild should not be used when present. On a typical Gentoo system,
>> /usr/local/ should be all but empty. If not, you may be endangering
>> the way portage works. Just be careful if you plan to keep doing
>> that ...
>
> There are some packages for which there are NO ebuilds,

In that case I usually write one (if none can be found on
bugs.gentoo.org). It's actually quite simple, if you know what you're
going to pass to ./configure. Checking for dependencies is a bit
trickier, but examining the various files will usually provide the
answers you need. Of course you can ignore dependencies if you're just
going to be using it locally.

> or for which the ebuilds are VERY out of date.

In that case I try to upgrade the ebuild. Very often a version rename
is sufficient for basic operation.

> One example is the gnu avr tools (gdb and compiler ebuilds out of
> date, NO avarice ebuild available)

Got any websites for those? I'd like to see if an ebuild is easy to
write. If it is, I'll be happy to do the work and submit it to
bugzilla.

> SO I will build these in /usr/local. Why would this break portage?

Perhaps that would not, but I've seen cases where people installed all
sorts of things outside portage, which resulted in strange compile
breaking later on. Of course it's mostly dangerous with libraries. My
main issue is that you lose automation and a record of what is installed
where.

> /usr/local should be invisable to the system.

Well, it's not. If a library is installed outside of portage, the
configure script will often pick it up, and it may very well be
incompatible, which portage would have blocked.

> Root usually doesn't even HAVE /usr/local in its path.

Check again. Unless you've changed something, it is indeed in the PATH.

--
PeKaJe

Your manuscript is both good and original, but the part that is good is
not original and the part that is original is not good. -- Samuel Johnson

Rolleston wrote:

>> One word: Ick. I have yet to see anyone provide a good reason why an
>> ebuild should not be used when present.
>
> Suppose you want to install packages under a non-root user account,
> and want all the libraries placed under "$HOME/lib", etc? I can't see
> a way to do that with "emerge".

Ah, I thought you meant to install it globally (in /usr/local/). I
don't see any problems with installing in a users $HOME. No compiles
would usually look there, so it would not break portage. Still, if
you're the administrator, you may as well use portage, as it's less
work.

--
PeKaJe

There's nothing like the face of a kid eating a Hershey bar.

Peter Jensen wrote:
[...]
>> Suppose you want to install packages under a non-root user account,
>> and want all the libraries placed under "$HOME/lib", etc? I can't see
>> a way to do that with "emerge".
>
> Ah, I thought you meant to install it globally (in /usr/local/). I
> don't see any problems with installing in a users $HOME. No compiles
> would usually look there, so it would not break portage. Still, if
> you're the administrator, you may as well use portage, as it's less
> work.

Ideally "emerge" would be designed so that non-admin users on a
multi-user system could use it to install a subset of available
packages locally.

R.

On Thu, 21 Oct 2004 16:16:24 -0600, ray <ray@zianet.com> wrote:

> Is there a list somewhere of what is available to 'emerge'?? I looked
> around the gentoo site but could not find anything. I'd like to see that
> first before I go out and get sources for tons of stuff (like
> 'lmsensors').
>
> thanks
>

A complet list can be found at http://packages.gentoo.org

--
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/

Albert wrote:

> I think .org distros are going to take a lot of importance.

You must have been living in a M$ cave, then; open source distros have
*always* been important - much more important than anything else.

In other words - I think you haven't got a clue what you're talking about.

Could you list me some .com distro's ?

--
J

Where does the shit go ?