Puppy Linux Discussion Forum :: View topic - PPKG Puppy Linux Package Handler

Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info

FAQ

Memberlist

Usergroups

Profile

The time now is Wed 19 Jun 2013, 19:32
All times are UTC - 4

Forum index » Advanced Topics » Puppy Projects

PPKG Puppy Linux Package Handler
Moderators: Flash, JohnMurga

View previous topic :: View next topic

Page 2 of 2 [21 Posts]

Goto page: Previous 1, 2

Author

Message

pstef

Joined: 31 Jul 2009
Posts: 18

Posted: Thu 29 Oct 2009, 08:17 Post subject:

Hugh wrote:

Quote:

But that's exactly what you're doing. You've made it impossible to apply different coding style. Without those stupid comments it would be as simple as typing #indent -kr ppkg.c new-ppkg.c

We would like to believe that for programmers and coding nothing is impossible. Finding the 'solution' is not always easy but with sufficient thought it will come forth without fail.

Comments, of course, are always optional, however, they can be very helpful to get the gist of the routines quickly and easily; thus leading to the 'big picture' with ease.

http://lxr.linux.no/#linux+v2.6.31/Documentation/CodingStyle#L425

Hugh

Joined: 24 Jun 2006
Posts: 134
Location: Imperial Warmongering Dystopia of Amerika

Posted: Thu 29 Oct 2009, 22:14 Post subject: Coding Styles
Subject description: Style recommendations

Quote:

Linux kernel coding style

This is a short document describing the preferred coding
style for the linux kernel.

Coding style is very personal, and I won't _force_ my views
on anybody, but this is what goes for anything that I have to
be able to maintain, and I'd prefer it for most other things too.

Please at least consider the points made here.

- - - - - - - - - - - - - - - - - - - - - -

Of course, there are several coding conventions and
for the sake of 'uniformity' certain styles are recom-
mended for certain projects.

But I haven't seen any examples of the 'alleged'
over-commenting.

With a little ingenuity, in the event the comments
prove an irritant, it is possible to eliminate them
with the editor 'search and replace' function.

With a little more ingenuity, it is even possible to
develop a program to re-style the source code.

For programmers, nothing is impossible.

pstef

Joined: 31 Jul 2009
Posts: 18

Posted: Sat 31 Oct 2009, 10:11 Post subject:

I don't want to keep talking off the topic, just let me say that I disagree with you.

scsijon

Joined: 23 May 2007
Posts: 948
Location: the australian mallee

Posted: Sat 02 Apr 2011, 23:28 Post subject: ??

did this get any further or was it abandoned?

BarryK
Puppy Master

Joined: 09 May 2005
Posts: 6874
Location: Perth, Western Australia

Posted: Sat 17 Nov 2012, 09:29 Post subject:

There is new action in this area:

http://bkhome.org/blog2/?viewDetailed=00028
_________________
http://bkhome.org/blog2/

scsijon

Joined: 23 May 2007
Posts: 948
Location: the australian mallee

Posted: Wed 28 Nov 2012, 20:24 Post subject: Re: Category-File

Wosh wrote:

The category file structure is very simple as it only assigns package-names to their category. If all distribution categories once have been classified their source does not matter. The package-names are unique and hopefully have the same categorisation for each distribution. A universal puppy.ctg would be enough. It even could include Slackware and Arch as long as the categorisation has same structure for all distributions.

Wosh, this is no longer a stable statementset.

The freedesktop.org group that is handling categories has updated and added to the standard sets.

Therefore 'old' packages will meet one of the old standards, but newly updated or added packages may or not use a later standard depending on if a builder/packager is using the specific standard.

It will also be important to consider that most distributions have a number of non-standard categories that differntiate only for that build and can have different package-group meanings to different distributions.

And then you get down to the 'use' of the linux machine and what the package-group names relate to, I can best give you a pointer to what I mean, by asking you to consider these two boxes!

Box 1 runs linux and is a business workstation, so it has applications such as openoffice, a finance package, a graphics package, email, firefox, etc. all grouped as "office" applications.
There are a number of these boxes in any adverage office.

Box2 runs linux, however it's a data and email server for a office, it also has logins, monitoring software as well as databases and other common user backends. For it, the words 'office applications' don't mean user applications, but applications it needs to run and monitor to keep it and the office it 'works for' running happily.

So depending on what the builder/packager considers the package will exist on in the end, will depend on what group it will be given.

That is why different .ctg files should be considered, but even then I'm not sure it's enough by itself.

Page 2 of 2 [21 Posts]

Goto page: Previous 1, 2

View previous topic :: View next topic

Forum index » Advanced Topics » Puppy Projects

Jump to:

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum

[ Time: 0.0610s ][ Queries: 13 (0.0083s) ][ GZIP on ]