public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: tastytea <gentoo@tastytea.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Change History of linux commands
Date: Fri, 7 Oct 2022 17:47:51 +0200	[thread overview]
Message-ID: <20221007174751.2cd99221@ventiloplattform.tastytea.de> (raw)
In-Reply-To: <e9e8dbd7-7161-9488-f068-28c48b035e12@web.de>

On 2022-10-07 17:25+0200 n952162 <n952162@web.de> wrote:

> Am 07.10.22 um 16:56 schrieb Grant Taylor:
> > On 10/7/22 8:25 AM, n952162 wrote:  
> >> Can anybody tell me how I can look at the official change history
> >> of linux commands?  
> >
> > Some man pages have history of commands in them.
> >
> > Admittedly, it seems as if man pages on Solaris and *BSD (I have
> > access to FreeBSD) tend to be better than Linux man page at this
> > aspect.
> >
> >
> >  
> 
> Well, the man page, yes, would be a good indicator, but the commands
> themselves?
> 
> Where does gentoo get the source to build  test(1) or expr(1) or
> date(1)?    That's in some package, but where is the upstream source? 
> Is it something in github?  Or a linux portal?  Or Torvalds private
> server?  Or the gnu server?
> 
> 

/usr/bin/test[1] was installed by sys-apps/coreutils[2], it's homepage
is <https://www.gnu.org/software/coreutils/>[3], that links to the
source code repository.

Other ways to find out:
  - `equery meta sys-apps/coreutils`
  - `less $(portageq get_repo_path / gentoo)/sys-apps/coreutils/coreutils-8.32-r1.ebuild`

Kind regards, tastytea

[1] `whereis test`
[2] `qfile /usr/bin/test` or `equery belongs /usr/bin/test`
[3] `eix sys-apps/coreutils` or emerge -s sys-apps/coreutils`


  reply	other threads:[~2022-10-07 15:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-07 14:25 [gentoo-user] Change History of linux commands n952162
2022-10-07 14:29 ` [gentoo-user] [RESOLVED] " n952162
2022-10-07 18:27   ` Alan J. Wylie
2022-10-07 14:56 ` [gentoo-user] " Grant Taylor
2022-10-07 15:25   ` n952162
2022-10-07 15:47     ` tastytea [this message]
2022-10-07 15:55       ` n952162
2022-10-07 15:57       ` Michael Orlitzky
2022-10-07 15:57       ` Laurence Perkins
2022-10-07 16:31       ` Matt Connell
2022-10-07 17:04         ` Grant Taylor
2022-10-07 17:10           ` Matt Connell
2022-10-07 17:39             ` Grant Taylor
2022-10-07 17:24         ` Dale
2022-10-09 15:59       ` Róbert Čerňanský
2022-10-07 16:23     ` Philip Webb
2022-10-07 17:07       ` Grant Taylor

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=20221007174751.2cd99221@ventiloplattform.tastytea.de \
    --to=gentoo@tastytea.de \
    --cc=gentoo-user@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