unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mario Lang <mlang@delysid.org>
To: emacs-devel@gnu.org
Subject: Re: [elpa] --exclude-vcs for multi-file archives?
Date: Thu, 22 May 2014 22:28:42 +0200	[thread overview]
Message-ID: <874n0h36dh.fsf@fx.delysid.org> (raw)
In-Reply-To: <87wqdd7n2q.fsf@fencepost.gnu.org> (David Kastrup's message of "Thu, 22 May 2014 19:14:21 +0200")

David Kastrup <dak@gnu.org> writes:

> Mario Lang <mlang@delysid.org> writes:
>
>> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>
>>>> $ make archive
>>>
>>> Where did you find a reference to this?
>>> It's an old deprecated way to build an archive.
>>
>> OK, was not aware that this method (albeit rather simple) is
>> deprecated.  I actually found it by skimming the GNUMakefile.
>
> If it isn't supported, it should be removed, right?  Exactly because
> people will use it upon discovering it.

"make archive-full", which is a variant of "make archive" is called from
admin/update-archive.sh.  My error was to "ignore" the preparation steps
done within that script, and manually call the make target which is
called from within that script after preparation.  Calling "make
archive" actually does a useful job for me, except for the missing
implicit extra excludes done by the update-archive.sh.

I guess I will keep things as they are, since "make archive" is
apparently not ment to be called directly.  That's not surprising, a
make target is not automatically public interface :-)

Thanks Stefan, for explaining the situation.  And sorry for the noise.

-- 
CYa,
  ⡍⠁⠗⠊⠕



  reply	other threads:[~2014-05-22 20:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-22 10:07 [elpa] --exclude-vcs for multi-file archives? Mario Lang
2014-05-22 14:05 ` Stefan Monnier
2014-05-22 14:35   ` Mario Lang
2014-05-22 16:09     ` Stefan Monnier
2014-05-22 16:55       ` Mario Lang
2014-05-22 17:14         ` David Kastrup
2014-05-22 20:28           ` Mario Lang [this message]
2014-05-23  0:58           ` Stefan Monnier

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874n0h36dh.fsf@fx.delysid.org \
    --to=mlang@delysid.org \
    --cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox

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

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 read-only IMAP folder(s) and NNTP newsgroup(s).