May 2008 - crux-devel - lists.crux.nu

[CRUX][#283] pkgmk, build from existing work dir
by CRUX 28 May '08

28 May '08

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#283 - pkgmk, build from existing work dir User who did this - Johannes Winkelmann (jw) ---------- Bartlomiej: Well, we _want_ people to be port maintainers, and build proper packages (using sed and diff/patch if needed); adding features which make it easier not to do that seems quite detrimental to that goal. As a more generic remark, it's very easy to extend pkgutils and add features, it's just not the goal. This approach may sometimes involve a little more work by the user, but keeps the system simpler overall. This patch is a good example of that. ---------- More information can be found at the following URL: http://crux.nu/bugs/index.php?do=details&task_id=283#comment403 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

1 0

[CRUX][#283] pkgmk, build from existing work dir
by CRUX 28 May '08

28 May '08

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#283 - pkgmk, build from existing work dir User who did this - Alan Mizrahi (alancio) ---------- I don't like the patch() build() and install() functions either, it just was the only solution I could think of. Another thing I have thought is that instead of using "-b" or "--build" it would be better to use something like "-bw" or "--build-work", or perhaps "-rw" "--resume-work", to make more clear what would happen. And instead of a variable named PKGMK_BUILD in /etc/pkgmk.conf, we could use PKGMK_RESUME_WORK, PKGMK_REUSE_WORK, or something like that. ---------- More information can be found at the following URL: http://crux.nu/bugs/index.php?do=details&task_id=283#comment402 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

1 0

[CRUX][#283] pkgmk, build from existing work dir
by CRUX 28 May '08

28 May '08

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#283 - pkgmk, build from existing work dir User who did this - Bartlomiej Palmowski (mxq) ---------- This is not adding features for sake of assing features, this is adding features that are helpful, #1 not everyone wants to be port maintainer nor have time for this, so this nifty option allows faster building and tweaking packages, #2 sometimes when i want to check quikly if certain applications build's ok, such option is a blessing, no mangling with sed or diff. alancio: thanks for support ;], I agree that created package shouldn't be deleted, but in my opinion patch() build() and install() functions are not necessary, and makes porting more complicated. ---------- More information can be found at the following URL: http://crux.nu/bugs/index.php?do=details&task_id=283#comment401 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

1 0

prtverify daily results
by crux＠crux.nu 28 May '08

28 May '08

Differences since last check: (no differences) Full report: http://crux.nu/files/prtverify.log

1 0

Potentially broken source downloads
by crux＠crux.nu 28 May '08

28 May '08

Port: /home/crux/git-to-rsync-working-copy/crux-2.4/opt/lsof Url: ftp://lsof.itap.purdue.edu/pub/tools/unix/lsof/lsof_4.79.tar.bz2 Reason: curl: (8) This doesn't seem like a nice ftp-server response State: Changed reason Full report: http://crux.nu/files/check_urls.html

1 0

[CRUX][#283] pkgmk, build from existing work dir
by CRUX 28 May '08

28 May '08

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#283 - pkgmk, build from existing work dir User who did this - Lucas Hazel (nipuL) ---------- It's one thing to say a feature is useful, it's an entirely different thing to explain why it is useful. I don't understand what problem this is trying to solve. The way I see it is features get added to pkgutils that solve a problem, adding features for the sake of adding features is not the CRUX way. ---------- More information can be found at the following URL: http://crux.nu/bugs/index.php?do=details&task_id=283#comment399 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

1 0

[CRUX][#283] pkgmk, build from existing work dir
by CRUX 28 May '08

28 May '08

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#283 - pkgmk, build from existing work dir User who did this - Alan Mizrahi (alancio) ---------- I like this patch, except that the -b option shouldn't delete the resulting package, print a warning should be enough. After all, this option is not enabled by default. A solution to the patching problem would be to have separate patch() build() and install() functions in Pkgfiles. When calling pkgmk with -b, only the build() and install() functions would be called. Note that this change wouldn't render current ports invalid, pkgmk could check for the existance of the patch() and install() functions, and only call them if they exist. ---------- More information can be found at the following URL: http://crux.nu/bugs/index.php?do=details&task_id=283#comment397 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

1 0

[CRUX][#283] pkgmk, build from existing work dir
by CRUX 27 May '08

27 May '08

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#283 - pkgmk, build from existing work dir User who did this - Bartlomiej Palmowski (mxq) ---------- Probably you're loosing my point, this feature would be handy for both maintainers and end users, it's not intended to be main tool for building ports, but merely helper in some cases, besides pkgmk would delete created port with -b option (but im not really sure if it should). ---------- More information can be found at the following URL: http://crux.nu/bugs/index.php?do=details&task_id=283#comment392 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

1 0

[CRUX][#283] pkgmk, build from existing work dir
by CRUX 27 May '08

27 May '08

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#283 - pkgmk, build from existing work dir User who did this - Lucas Hazel (nipuL) ---------- The problem I see with this feature is the possibility of compiling patched code without knowing it. It's better to build from clean sources. ---------- More information can be found at the following URL: http://crux.nu/bugs/index.php?do=details&task_id=283#comment391 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

1 0

prtverify daily results
by crux＠crux.nu 27 May '08

27 May '08

Differences since last check: (no differences) Full report: http://crux.nu/files/prtverify.log

1 0