From: Michael Witten <mfwitten@gmail.com>
To: Ali Tofigh <alix.tofigh@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: many files, simple history
Date: Thu, 13 May 2010 22:27:42 -0500 [thread overview]
Message-ID: <AANLkTimHB9jZq-SUxD2YUfCXKfTOHSxEnANETDL7i6DB@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinHZbJ4obpa1FpT8boFWjNYpgU184HUTvki_A0G@mail.gmail.com>
On Thu, May 13, 2010 at 21:57, Ali Tofigh <alix.tofigh@gmail.com> wrote:
> (i almost
> always build from source code and install in non-standard locations).
It would make a lot more sense to use a package manager.
You might find that Arch Linux's `pacman' provides everything that you
need; it's really easy to define your own packages and build from
source, allowing pacman to manage dependencies, locate which package
owns which file, and upgrade/remove packages.
I bet gentoo's `emerge' would also be viable.
next prev parent reply other threads:[~2010-05-14 3:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-14 2:57 many files, simple history Ali Tofigh
2010-05-14 3:27 ` Michael Witten [this message]
2010-05-14 16:25 ` Ali Tofigh
2010-05-14 4:05 ` Jeff King
2010-05-14 16:18 ` Ali Tofigh
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=AANLkTimHB9jZq-SUxD2YUfCXKfTOHSxEnANETDL7i6DB@mail.gmail.com \
--to=mfwitten@gmail.com \
--cc=alix.tofigh@gmail.com \
--cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).