all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: Nils Gillmann <niasterisk@grrlz.net>
Cc: guix-devel@gnu.org
Subject: Re: Needs new category/file: Reverse Engineering Software
Date: Wed, 17 Feb 2016 23:35:35 +0100	[thread overview]
Message-ID: <20160217223535.GA32658@solar> (raw)
In-Reply-To: <87io1no0zx.fsf@grrlz.net>

Hi Nils,

On Wed, Feb 17, 2016 at 03:38:42PM +0100, Nils Gillmann wrote:
> 
> As this doesn't do the job for me, I propose
> gnu/packages/disassembler.scm
> or
> gnu/packages/re.scm
> or
> gnu/packages/reverse-engineering.scm
> as it specifies an existing category of software and is not just
> another debugger.

the first and the last of these are fine; I would avoid "re" as it is not
a word, and it is not clear at all what it is supposed to represent.

> Reverse engineering typically makes use of Debuggers,
> Disassemblers, Hex Editors and PE and Resource Viewers. A
> new category could be used to cut down on category files maybe
> get some existing, non-specific software into the new created
> category.

Do I understand correctly that you wish to move existing software into
the new module (=file)? Why not if you do the work :-)
Moving packages around is somewhat boring work and needs to be done
carefully, since all the "use-module" clauses in files where the package
is used need to be adapted.

Andreas

  reply	other threads:[~2016-02-17 22:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-17 14:38 Needs new category/file: Reverse Engineering Software Nils Gillmann
2016-02-17 22:35 ` Andreas Enge [this message]
2016-02-18 14:33   ` Nils Gillmann
2016-02-18 19:29     ` Andreas Enge
2016-02-18 14:45   ` Package modules Fabian Harfert
2016-02-29  9:52     ` Ludovic Courtès

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=20160217223535.GA32658@solar \
    --to=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    --cc=niasterisk@grrlz.net \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.