public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jeremy Maitin-Shepard <jbms@gentoo.org>
To: gentoo-portage-dev@gentoo.org
Subject: [gentoo-portage-dev] portage-ng ideas
Date: Tue, 16 Dec 2003 19:52:48 -0500	[thread overview]
Message-ID: <87iskge04f.fsf@jbms.ath.cx> (raw)

I have the following ideas for portage-ng requirements.  If one or more
of them has already been stated and/or discussed, please disregard it.

 - More powerful functionality during the merge phase than simple file
   and directory creation/replacement.  Specifically, it would be
   useful to support other actions like user or group creation.
   Furthermore, it would be useful to support addition of new `action'
   types (without modifying portage code), i.e. in an ebuild or an
   eclass or some other system designed for this purpose.  This would
   be useful for things such as the emacs site lisp, /etc/init.d/
   scripts, kernel modules, /etc/env.d/ scripts, /etc/modules.d/
   scripts.  The current practice for init.d, env.d and modules.d seems
   to be to rebuild the cached files relating to these directories
   after every package merge; support of `custom' `action' types would
   be a more elegant solution.

 - Possibly improving efficiency by creating a portage temporary
   directory (or allow the user to create and specify the existence of
   such a directory) on each filesystem (or on several filesystem) to
   which portage will install files.  By using bind mounts, the image
   temp directory could be constructed so that the files that will be
   installed on a particular filesystem for which there is a temporary
   directory would be installed in the portage temporary directory of
   that filesystem.  This would allow the merge phase to create hard
   links (or move) rather than copying, which would be faster and allow
   for less temporary use of disk space.  I realize though that the
   implementation difficulty of this might outweigh the advantages.
   Furthermore, it might be problematic if portage did not auto-clean
   (auto-delete) the files with link counts > 1.  Now that I consider
   this though, I realize that during the build phase, files will be
   installed in a temporary directory on a different filesystem, and so
   there is still the need to copy.

-- 
Jeremy Maitin-Shepard

--
gentoo-portage-dev@gentoo.org mailing list


                 reply	other threads:[~2003-12-17  0:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=87iskge04f.fsf@jbms.ath.cx \
    --to=jbms@gentoo.org \
    --cc=gentoo-portage-dev@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