From: Ali Tofigh <alix.tofigh@gmail.com>
To: Michael Witten <mfwitten@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: many files, simple history
Date: Fri, 14 May 2010 12:25:52 -0400 [thread overview]
Message-ID: <AANLkTinZ4MuAofDwhx6FZjlY6fU7_sdgIZlg7RRMH1C8@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimHB9jZq-SUxD2YUfCXKfTOHSxEnANETDL7i6DB@mail.gmail.com>
On Thu, May 13, 2010 at 23:27, Michael Witten <mfwitten@gmail.com> wrote:
> 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're probably right, but if i want to keep up with all my everyday
obligations, then i have to chose my battles carefully. for many
tasks, there are specialized tools that can be used, but these always
come at the expense of having to learn them. and if those tasks aren't
performed on a daily basis, then i don't stand a chance at remembering
what i've learned and i have to relearn them over and over again.
/ali
>
> 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 16:26 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
2010-05-14 16:25 ` Ali Tofigh [this message]
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=AANLkTinZ4MuAofDwhx6FZjlY6fU7_sdgIZlg7RRMH1C8@mail.gmail.com \
--to=alix.tofigh@gmail.com \
--cc=git@vger.kernel.org \
--cc=mfwitten@gmail.com \
/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).