diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-October/009247.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-October/009247.html | 126 |
1 files changed, 126 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-October/009247.html b/zarb-ml/mageia-dev/2011-October/009247.html new file mode 100644 index 000000000..049f8facd --- /dev/null +++ b/zarb-ml/mageia-dev/2011-October/009247.html @@ -0,0 +1,126 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Please test: initscripts+systemd in updates_testing + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Please%20test%3A%20initscripts%2Bsystemd%20in%20updates_testing&In-Reply-To=%3C4EAEF3CD.7000302%40mageia.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="009245.html"> + <LINK REL="Next" HREF="009148.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Please test: initscripts+systemd in updates_testing</H1> + <B>Thomas Backlund</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Please%20test%3A%20initscripts%2Bsystemd%20in%20updates_testing&In-Reply-To=%3C4EAEF3CD.7000302%40mageia.org%3E" + TITLE="[Mageia-dev] Please test: initscripts+systemd in updates_testing">tmb at mageia.org + </A><BR> + <I>Mon Oct 31 20:15:25 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="009245.html">[Mageia-dev] Please test: initscripts+systemd in updates_testing +</A></li> + <LI>Next message: <A HREF="009148.html">[Mageia-dev] Please test: initscripts+systemd in updates_testing +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#9247">[ date ]</a> + <a href="thread.html#9247">[ thread ]</a> + <a href="subject.html#9247">[ subject ]</a> + <a href="author.html#9247">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Colin Guthrie skrev 31.10.2011 19:54: +><i> [Sorry for multiple replies, missed this bit in the last one :s] +</I>><i> +</I>><i> 'Twas brillig, and Thomas Backlund at 31/10/11 17:06 did gyre and gimble: +</I>>><i> But I guess that's the development trend nowdays: "I cant be bothered to +</I>>><i> fix things properly so I just call it "depreceated"... and go ahead +</I>>><i> and break things just as I like" +</I>><i> +</I>><i> +</I>><i> I think that's a little unfair in the representation of this problem (I +</I>><i> won't comment if this *is* an overall trend). +</I>><i> +</I> +Yeah, I guess I'm blowing some steam based on some misunderstandings +regarding this problem :) + +On the overall trend I think it still stands, atleast for many companies +that I have had to deal with when they deliver +apps/"cloud *"/... that does not work even closly to how it's supposed +to... :/ + +<ot> +One _big_ company built a new ticket ordering system, and when they +send the tickets by mail they will be sent as pdf. so far so good. +But then the guy responsible for the coding pretty much thougth +"hey its a file that is in pdf format, so lets set the mimetype to +file/pdf". and even if I have pointed out many times that there is +no such thing, it's still not fixed. + +An other companys booking system showes the whole booking info +that belongs in the mail body in the mail header. and when I +pointed out the problem, the response was pretty much "it's too +hard to fix", and since mailservers can cope with it, I guess it +will never be fixed... + +I could go on, but this is just the two last incidents I have +had to work around and it seems it just happends more and more... +</ot> + +><i> I think there has been a significant push recently to break from +</I>><i> "traditions" that are holding things back. If something doesn't work *by +</I>><i> design* then coming up with an alternative way of working and +</I>><i> deprecating the old way seems like a perfect way of driving progress IMO. +</I>><i> +</I> +Yeah, in some cases deprecating is unavoidable, that's true, in other +cases it seems to have been done too easily. + +><i> The "I can't be bothered to fix things properly" could easily be applied +</I>><i> to the current status quo, which has a carefully ordered sequence of +</I>><i> otherwise parallelisable tasks and a careful placement of certain key +</I>><i> files, just because no one can "be bothered" to address the underlying +</I>><i> design issues. +</I>><i> +</I> +touché :) + +><i> I guess it's likely just a matter of perspective/opinion as to which +</I>><i> philosophy "can't be bothered". +</I> +Yeah, +but it's always good to get perspective/opinions from several points in +order to get a good product in the end :) + +-- +Thomas + +</PRE> + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="009245.html">[Mageia-dev] Please test: initscripts+systemd in updates_testing +</A></li> + <LI>Next message: <A HREF="009148.html">[Mageia-dev] Please test: initscripts+systemd in updates_testing +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#9247">[ date ]</a> + <a href="thread.html#9247">[ thread ]</a> + <a href="subject.html#9247">[ subject ]</a> + <a href="author.html#9247">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev +mailing list</a><br> +</body></html> |