public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Diego 'Flameeyes' Pettenò" <flameeyes@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Discussion: alternative compatible utilities
Date: Thu, 16 Jun 2005 07:57:14 +0200	[thread overview]
Message-ID: <200506160757.19214@enterprise.flameeyes.is-a-geek.org> (raw)

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

As Gentoo/FreeBSD proceeds, I'm trying to abstract as much as I can the 
underlying userland.
Thinking of Gentoo/FreeBSD just as a starting point for other porting of 
Gentoo's framework on different operating systems (for example the 
already-work-in-progress Gentoo/Darwin, the I-don't-know-how's-doing 
Gentoo/OpenBSD, and the maybe-someone-will-work-on Gentoo/NetBSD), there's 
something I'd really like to see: alternatives for system utilities.

Let me explain: on Gentoo/Linux systems, all the base utilities (make, tar, 
sed, etc etc) are GNUish; on Gentoo/FreeBSD they are BSDish; on Gentoo/Darwin 
I don't really know :P
This limits a bit the user because to use other kind of utilities it must use 
aliases and he can't change, for example, the tar used by portage or by other 
scripts.

As eselect's work is proceeding it can be interesting having a way to have the 
base utils install with a prefix (g for GNU stuff, bsd for BSD stuff, 
eventually fbsd/obsd/nbsd if they are different) and then having a link to 
the basename which acn be changed with eselect.
Most of the scripts which needs a specific syntax (usually GNU syntax) already 
checks for prefixed executables like gmake, gsed and so on, but the main 
problem is with portage (think of all the make DESTDIR="${D} install stuff), 
also if emake is fixed and sed stuff is as compatible as possible.

Having to provide compatibility with such a framework is quite difficult at 
this point because many ebuilds does depend on GNU syntax also if not clearly 
stated, but I hope this can be fixed step-by-step using g-prefixed commands 
(after making sure that all systems will have g-prefixed commands).
It's not like something is going to happen soon, but maybe in the future this 
can be a good way to make sure we expand the abiliy of users to select what 
they really want.

Comments, ideas, and everythign else is welcome, it's a discussion after all.

-- 
Diego "Flameeyes" Pettenò
Gentoo Developer (Gentoo/FreeBSD, Video, Gentoo/AMD64)

http://dev.gentoo.org/~flameeyes/


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

             reply	other threads:[~2005-06-16  6:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-16  5:57 Diego 'Flameeyes' Pettenò [this message]
2005-06-16  8:26 ` [gentoo-dev] Discussion: alternative compatible utilities Luca Barbato
2005-06-16 11:18   ` Dan Meltzer
2005-06-17  2:32 ` Aron Griffis
2005-06-17 14:05   ` Diego 'Flameeyes' Pettenò
2005-06-18 11:23     ` Martin Schlemmer
2005-06-21 18:45       ` Aron Griffis
2005-07-05 10:37         ` Martin Schlemmer
2005-06-21 18:42     ` Aron Griffis
2005-06-21 18:57       ` Diego 'Flameeyes' Pettenò
2005-06-18  3:29   ` Grant Goodyear
  -- strict thread matches above, loose matches on Subject: below --
2005-06-16 21:26 Alec Warner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200506160757.19214@enterprise.flameeyes.is-a-geek.org \
    --to=flameeyes@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox