Package Details: tup-git 0.7.11.r95.g4e9f5b32-1

Git Clone URL: (read-only, click to copy)
Package Base: tup-git
Description: A fast, file-based build system
Upstream URL:
Licenses: GPL2
Conflicts: tup
Provides: tup
Submitter: pnorcks
Maintainer: pica
Last Packager: pica
Votes: 7
Popularity: 0.000001
First Submitted: 2010-03-09 02:09 (UTC)
Last Updated: 2023-01-30 22:17 (UTC)

Dependencies (2)

Required by (6)

Sources (1)

Latest Comments

1 2 3 Next › Last »

pyropeter commented on 2014-03-04 00:10 (UTC)

Great, yet another piece of fine software in [community]! But now you put a replaces-option into this PKGBUILD? Are you sure you know what that does? And the provides-option is still missing.

anatolik commented on 2014-03-03 18:04 (UTC)

Actually tup is in [community] now.

pyropeter commented on 2014-03-03 18:00 (UTC)

Since this is an alternative to the tup package, could you please specify the following: provides=('tup') conflicts=('tup') Furthermore, I think that the tup package should be discontinued, since it is outdated and unmaintained (well, I just adopted it, but that was before I saw this package), and the upstream doesn't even provide tarball releases. Anatolik, could you delete it?

anatolik commented on 2013-08-29 01:06 (UTC)

Thanks spider-mario, your changes are applied.

spider-mario commented on 2013-08-28 12:42 (UTC)

There is upstream support for vim and this patch would enable it:

Deewiant commented on 2013-08-28 10:28 (UTC)


anatolik commented on 2013-08-28 10:19 (UTC)

Ok, busybox uses filesystem to preserve "variable". Let's use it for tup. Deewiant@ thanks for the feature request. It should be ready now.

Deewiant commented on 2013-08-28 06:32 (UTC)

Take a look at busybox.install, it seems to preserve the busybox binary's mode across pre/post_upgrade. It simply saves the original mode to a file in a local tmp directory which it then deletes. Also, side note: tup doesn't use the suid bit only for full dependency tracking: the 'c' flag on ^ commands is another case. Thus the suid_msg in the draft is maybe a bit misleading.

anatolik commented on 2013-08-28 02:52 (UTC)

Here is a draft for tup.install but unfortunately I do not see a way how to preserve a variable between pre_upgrade and post_upgrade phases. Just setting the variable does not work. Any ideas?

Deewiant commented on 2013-08-27 17:30 (UTC)

Oh, well then that's not such a good citation for "normal practice". :-) Nevertheless I don't think we should be setting any particular precedent here, so I'd say go with the preservation + message.